Jira MCP Server (Atlassian)
Official Atlassian MCP server providing agent-native tools for searching, creating, and updating Jira issues and projects — enabling agents to interact with Jira Cloud without constructing raw REST calls or managing JQL queries manually.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
OAuth 2.0 with fine-grained read/write scopes for Jira data. API tokens are user-scoped and can be revoked individually. SOC2 Type II and ISO 27001 certified. FedRAMP authorization in progress. Data residency options for EU and AU.
⚡ Reliability
Best When
An agent needs to read, create, and update Jira issues and manage sprint workflows as part of development lifecycle automation in a Jira Cloud environment.
Avoid When
The task requires deep administrative configuration of Jira workflows, permission schemes, or custom field schemas — these are outside the MCP server's scope.
Use Cases
- • Search issues using JQL to find bugs, tasks, or stories matching specific criteria for triage workflows
- • Create and update tickets programmatically as part of automated development or incident management pipelines
- • Manage sprint contents and transition issue statuses to drive agile workflow automation
- • Link related issues and epics to maintain project graph structure from agent-generated insights
- • Query project boards and backlogs to generate sprint planning summaries or velocity reports
Not For
- • Full project administration — complex workflow, permission scheme, or field configuration changes are not exposed via the MCP tools
- • Complex custom workflow automation requiring Jira Automation rules or ScriptRunner — use those tools directly
- • Bulk data migrations — the MCP interface is not optimized for high-volume import/export operations
Interface
Authentication
Jira Cloud requires Atlassian API token (email + token basic auth) or OAuth 2.0 (3LO). Basic auth with password is deprecated — must use API token. OAuth 2.0 supports fine-grained scopes for read:jira-work and write:jira-work. Server/Data Center uses different auth mechanisms.
Pricing
MCP server itself is open source. Jira Cloud subscription required for API access. API access is included with all Jira plans including Free.
Agent Metadata
Known Gotchas
- ⚠ JQL (Jira Query Language) syntax must be learned — even small syntax errors return 400 errors with sometimes cryptic messages
- ⚠ Issue key (PROJECT-123), issue ID (numeric), and internal UUID are three different identifiers used in different contexts — mixing them causes confusing 404s
- ⚠ Status transitions require the transition ID (numeric), not the transition name — agents must first fetch available transitions for an issue before transitioning
- ⚠ Custom fields have project-specific IDs (customfield_10001 etc.) that differ between Jira instances — field IDs are not portable
- ⚠ Basic auth with password is deprecated — must use API token with email as username; using the account password directly no longer works
- ⚠ Jira Cloud and Jira Server/Data Center have meaningfully different API surfaces — MCP server targets Cloud only
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Jira MCP Server (Atlassian).
Scores are editorial opinions as of 2026-03-06.