jira-mcp-server

jira-mcp-server

Exposes JIRA sprint data as MCP tools and prompts, with mock data and a pluggable client for real JIRA integration.

Category
访问服务器

README

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 get_active_sprint_issues, get_issue_details
Prompts format_sprint_progress, format_issue_details
Data layer Abstract JiraClient — swap mock ↔ real API via env var
Models Pydantic v2 with full type safety

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_details

Quick Start

Prerequisites

  • Python 3.12+
  • uv (recommended) or pip

Install dependencies

uv sync

Run the server

# Using the installed script:
uv run jira-mcp-server

# Or directly:
uv run python main.py

The 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-server

MCP 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:

  1. 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=PROJ
    
  2. Fill in the TODO sections in src/jira/api_client.py:

    • Uncomment the httpx import and install httpx (uv add httpx)
    • Implement get_sprint_issues, get_issue, and get_sprint_meta using the JIRA Agile REST API v1 and REST API v3 endpoints documented inline
  3. Restart the server — the factory auto-selects ApiJiraClient when JIRA_API_TOKEN is present.

No changes to tools, prompts, or server code are required.


Development

Inspect with MCP Inspector

uv run mcp dev main.py

Opens 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.py

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选