JIRA integration server for Model Context Protocol (MCP) - enables LLMs to interact with JIRA tasks and workflows
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.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| 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 |
{
"mcpServers": {
"mcp-jira": {
"command": "/path/to/mcp-jira/.venv/bin/python",
"args": [
"-m",
"mcp_jira"
]
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
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.