jira-mcp-server
Allows interaction with JIRA sprint data, providing tools to get active sprint issues and issue details, and prompts to format sprint progress and issue details.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jira-mcp-servershow active sprint issues for Platform Engineering"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JIRA MCP Server
A production-grade Model Context Protocol (MCP) server that exposes JIRA sprint data as MCP Tools and Prompts.
Ships with rich in-memory mock data (30 issues, 8 assignees) and a pluggable JiraClient abstraction that makes connecting to a real Atlassian JIRA instance a drop-in upgrade.
Features
Category | Detail |
Transport | SSE (HTTP) — compatible with Cursor, Claude.ai Web, and any SSE-capable MCP client |
Tools |
|
Prompts |
|
Data layer | Abstract |
Models | Pydantic v2 with full type safety |
Related MCP server: jtk
Project Structure
jira-mcp-server/
├── main.py # Entry point (SSE server)
├── pyproject.toml
└── src/
├── data/
│ ├── models.py # Pydantic v2 models (JiraIssue, Assignee, SprintMeta)
│ └── mock_issues.py # 30 mock issues + SPRINT_META
├── jira/
│ ├── __init__.py # get_jira_client() factory
│ ├── base.py # Abstract JiraClient (ABC)
│ ├── mock_client.py # MockJiraClient — in-memory fixture data
│ └── api_client.py # ApiJiraClient — real JIRA REST stub
├── server/
│ ├── app.py # FastMCP instance + client initialisation
│ └── tools.py # @mcp.tool registrations
└── prompts/
├── sprint_progress.py # @mcp.prompt: format_sprint_progress
└── issue_details.py # @mcp.prompt: format_issue_detailsQuick Start
Prerequisites
Python 3.12+
uv (recommended) or pip
Install dependencies
uv syncRun the server
# Using the installed script:
uv run jira-mcp-server
# Or directly:
uv run python main.pyThe SSE server starts at http://localhost:8000/sse by default.
Override host/port via environment variables:
MCP_HOST=127.0.0.1 MCP_PORT=9000 uv run jira-mcp-serverMCP Client Configuration
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"jira": {
"url": "http://localhost:8000/sse"
}
}
}Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"jira": {
"url": "http://localhost:8000/sse"
}
}
}Tools
get_active_sprint_issues
Returns all issues in the active sprint for the provided Scrum board name as a JSON array.
{ "scrum_board_name": "Platform Engineering Scrum Board" }get_issue_details
Returns the full details of a single issue.
{ "issue_id": "PROJ-1" }Raises an error if the issue key does not exist.
Prompts
format_sprint_progress
Generates a comprehensive scrum master report in Markdown:
Sprint Overview table (totals, velocity, completion %)
Blockers section (table + impact analysis per blocker)
Risk Analysis (Critical + High items not Done)
Resource Utilisation table (per-assignee: issues, SP, completion %)
Bandwidth Analysis (overloaded / under-utilised members + rebalancing suggestions)
Key Insights (patterns, anomalies)
Recommended Next Steps (prioritised action list)
{
"sprint_data_json": "{\"sprint_meta\":{...},\"issues\":[...]}"
}sprint_data_json should be the JSON payload returned by tools (metadata + issues),
or an issues-only JSON array.
format_issue_details
Renders a single issue as a structured Markdown document with:
Header (ID + Summary + Type + Status + Priority)
Metadata table (all fields)
Description section
Acceptance Criteria checklist (auto-checked if status = Done)
Labels
{
"issue_json": "{\"id\":\"PROJ-5\",...}"
}issue_json should be the JSON object returned by get_issue_details.
Connecting to Real JIRA
The JiraClient abstraction makes this a configuration-only change:
Set the following environment variables:
JIRA_BASE_URL=https://your-org.atlassian.net JIRA_EMAIL=service-account@your-org.com JIRA_API_TOKEN=your-atlassian-api-token JIRA_BOARD_ID=3 JIRA_PROJECT_KEY=PROJFill in the
TODOsections in src/jira/api_client.py:Uncomment the
httpximport and installhttpx(uv add httpx)Implement
get_sprint_issues,get_issue, andget_sprint_metausing the JIRA Agile REST API v1 and REST API v3 endpoints documented inline
Restart the server — the factory auto-selects
ApiJiraClientwhenJIRA_API_TOKENis present.
No changes to tools, prompts, or server code are required.
Development
Inspect with MCP Inspector
uv run mcp dev main.pyOpens the interactive MCP Inspector in your browser with all tools and prompts available for testing.
Static analysis
uv run mypy src/ main.py
uv run ruff check src/ main.pyThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aswin-sankaranarayanan/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server