jira-mock-mcp
Provides tools for interacting with a Jira instance, enabling management of projects, issues, comments, and users via a Jira-compatible API.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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/docsAzure NSG: Open inbound ports 3000 (frontend) and 8000 (API) in your Network Security Group.
Related MCP server: Jira MCP Server
ποΈ 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 |
| List all projects |
POST |
| Create project |
GET |
| Get project |
DELETE |
| Delete project |
GET |
| List/filter issues |
POST |
| Create issue |
GET |
| Get issue + comments |
PUT |
| Update issue |
DELETE |
| Delete issue |
POST |
| Move status |
GET |
| List comments |
POST |
| Add comment |
GET |
| JQL search |
GET |
| List users |
GET |
| Dashboard stats |
Full interactive docs at http://<host>:8000/docs
π€ MCP Server
Tools Available
Tool | Description |
| List all projects |
| Create a project |
| Get project details |
| Delete a project |
| List/filter issues |
| Create an issue |
| Get issue + comments |
| Update issue fields |
| Delete an issue |
| Change issue status |
| Comment on an issue |
| List issue comments |
| List available users |
| JQL search |
| 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>:8000and 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 |
|
| 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 URLAdd
JIRA_API_TOKENandJIRA_USERenv vars to the MCP serverUpdate
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Remote MCP for Kanban AI boardsβmanage projects, tasks, and comments from AI tools.
Nifty's MCP server β exposes tasks, projects, messages, and files as tools for AI agents.
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.63MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for Atlassian Jira that enables AI assistants to manage issues, sprints, comments, and worklogs through natural language.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with self-hosted Jira instances for issue management, search, comments, and workflow transitions.19MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira instances via the Model Context Protocol, providing 36 tools for reading and writing issues, projects, sprints, metrics, and more.24 npm2MIT