jira-mock-mcp
Enables AI assistants to interact with a self-hosted Jira clone for testing, supporting project and issue management, comments, and search via MCP tools.
README
PurpleTrack — JiraMock
A self-hosted Jira clone designed for testing MCP (Model Context Protocol) integrations on Azure. Ships with a REST API, MCP server, and purple web frontend — all in Docker.
🚀 Quick Start (Azure VM)
# 1. Clone the repo on your VM
git clone https://github.com/YOUR_ORG/jira-clone.git
cd jira-clone
# 2. Build and launch
docker compose up -d --build
# 3. Access
# Frontend: http://<VM_IP>:3000
# API: http://<VM_IP>:8000
# API Docs: http://<VM_IP>:8000/docs
Azure NSG: Open inbound ports 3000 (frontend) and 8000 (API) in your Network Security Group.
🏗️ Architecture
┌─────────────────────────────────────────┐
│ Docker Network │
│ │
│ ┌──────────┐ ┌──────────────────┐ │
│ │ Frontend │ │ Backend │ │
│ │ nginx │───▶│ FastAPI + JSON │ │
│ │ :3000 │ │ DB :8000 │ │
│ └──────────┘ └──────────────────┘ │
│ ▲ │
│ ┌──────────────────┐ │ │
│ │ MCP Server │───┘ │
│ │ (stdio/Python) │ │
│ └──────────────────┘ │
└─────────────────────────────────────────┘
📡 REST API
The API mirrors Jira's REST API v3 structure. All endpoints at /rest/api/3/.
| Method | Endpoint | Description |
|---|---|---|
| GET | /rest/api/3/project |
List all projects |
| POST | /rest/api/3/project |
Create project |
| GET | /rest/api/3/project/{key} |
Get project |
| DELETE | /rest/api/3/project/{key} |
Delete project |
| GET | /rest/api/3/issue |
List/filter issues |
| POST | /rest/api/3/issue |
Create issue |
| GET | /rest/api/3/issue/{key} |
Get issue + comments |
| PUT | /rest/api/3/issue/{key} |
Update issue |
| DELETE | /rest/api/3/issue/{key} |
Delete issue |
| POST | /rest/api/3/issue/{key}/transitions |
Move status |
| GET | /rest/api/3/issue/{key}/comment |
List comments |
| POST | /rest/api/3/issue/{key}/comment |
Add comment |
| GET | /rest/api/3/search?jql=... |
JQL search |
| GET | /rest/api/3/users |
List users |
| GET | /rest/api/3/stats |
Dashboard stats |
Full interactive docs at http://<host>:8000/docs
🤖 MCP Server
Tools Available
| Tool | Description |
|---|---|
list_projects |
List all projects |
create_project |
Create a project |
get_project |
Get project details |
delete_project |
Delete a project |
list_issues |
List/filter issues |
create_issue |
Create an issue |
get_issue |
Get issue + comments |
update_issue |
Update issue fields |
delete_issue |
Delete an issue |
transition_issue |
Change issue status |
add_comment |
Comment on an issue |
list_comments |
List issue comments |
list_users |
List available users |
search_issues |
JQL search |
get_stats |
Dashboard statistics |
Claude Desktop Config
Add to your claude_desktop_config.json:
{
"mcpServers": {
"jiramock": {
"command": "docker",
"args": [
"exec", "-i", "jiramock-mcp",
"python", "server.py"
],
"env": {
"JIRA_BASE_URL": "http://backend:8000"
}
}
}
}
Azure AI Foundry / HTTP MCP config
If your MCP client supports HTTP transport, point it at:
http://<VM_IP>:8000
and use the REST endpoints directly, or wrap the MCP server behind an SSE/HTTP proxy.
📁 Project Structure
jira-clone/
├── backend/
│ ├── main.py # FastAPI application
│ ├── requirements.txt
│ └── Dockerfile
├── mcp-server/
│ ├── server.py # MCP server (stdio transport)
│ ├── requirements.txt
│ └── Dockerfile
├── frontend/
│ ├── index.html # Purple web UI
│ └── Dockerfile
├── nginx/
│ └── default.conf # Reverse proxy config
├── docker-compose.yml
└── README.md
🔧 Configuration
| Variable | Default | Description |
|---|---|---|
JIRA_BASE_URL |
http://backend:8000 |
MCP server → backend URL |
Data is persisted in a Docker volume (jiramock-data) at /data/db.json.
🛑 Management
# Stop
docker compose down
# Stop and wipe data
docker compose down -v
# Logs
docker compose logs -f backend
docker compose logs -f mcp-server
# Rebuild after changes
docker compose up -d --build
🔁 Migrating to Real Jira
When ready to swap to real Jira:
- Replace
JIRA_BASE_URLwith your Jira instance URL - Add
JIRA_API_TOKENandJIRA_USERenv vars to the MCP server - Update
server.pyto use basic auth:httpx.AsyncClient(auth=(user, token))
The MCP tool interface remains identical — no changes to your Claude prompts or Azure Foundry config.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。