JIRA integration server for Model Context Protocol (MCP) - enables LLMs to interact with JIRA tasks and workflows
MCP Jira Integration MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. JIRA integration server for Model Context Protocol (MCP) - enables LLMs to interact with JIRA tasks and workflows.
A simple Model Context Protocol (MCP) server for Jira that allows LLMs to act as project managers and personal assistants for teams using Jira. Built on the Jira REST API v3.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once MCP Jira Integration is connected, these are the calls the assistant has available:
create_issue — Create new Jira issues with proper formatting and ADF descriptionssearch_issues — Search issues using JQL with smart formatting and paginationget_sprint_status — Get comprehensive sprint progress reports with metricsget_team_workload — Analyze team member workloads and capacitygenerate_standup_report — Generate daily standup reports automaticallyReliability — The Reliability tool exposed by this serverYou will need 4 environment variables: JIRA_URL, JIRA_API_TOKEN, PROJECT_KEY, DEFAULT_BOARD_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Jira Integration's toolset — create_issue, search_issues, get_sprint_status and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Warzuponus; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Jira Integration's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| create_issue | Create new Jira issues with proper formatting and ADF descriptions |
| search_issues | Search issues using JQL with smart formatting and pagination |
| get_sprint_status | Get comprehensive sprint progress reports with metrics |
| get_team_workload | Analyze team member workloads and capacity |
| generate_standup_report | Generate daily standup reports automatically |
| Reliability | The Reliability tool exposed by this server. |
{
"mcpServers": {
"mcp-jira": {
"command": "/path/to/mcp-jira/.venv/bin/python",
"args": ["-m", "mcp_jira"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_URL | Endpoint or connection string the server talks to. | Yes |
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| PROJECT_KEY | Credential the server authenticates with. | Yes |
| DEFAULT_BOARD_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.