Ranked roundup · Jira
Best MCP Server for Jira
Picking an MCP server for Jira is easier than it is for most tools, because Atlassian actually ships an official one. The Atlassian Remote MCP Server is generally available, runs hosted at mcp.atlassian.com, and covers Jira, Confluence, Jira Service Management, Bitbucket, and Compass over OAuth 2.1 — but it only works with Atlassian Cloud. The community fills the gap that leaves: sooperset/mcp-atlassian (5,820 GitHub stars, MIT, pushed August 28, 2026) is the self-hosted server that also talks to Jira Server and Data Center installs, which the official server does not. Managed platforms — Composio and Zapier — wrap Jira in hosted MCP endpoints for teams that would rather not run or configure anything. We ranked the five options below on verifiable criteria only: official status, maintenance recency, adoption, auth model, and documented capability coverage, checked against the GitHub API and vendor docs on September 1, 2026. Nobody paid for placement, and every caveat we found is listed.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Atlassian
Jira Cloud teams who want the vendor-supported, zero-hosting path with OAuth and official support
Search Jira with JQL, read issue details, create and update issues, and work across Confluence, Jira Service Management, Bitbucket, and Compass from one endpoint; generally available, with one-click setup for Cursor and documented support for Claude, ChatGPT, VS Code, and Gemini CLI
Fully hosted by Atlassian at mcp.atlassian.com — no install; connect via the remote URL, with an mcp-remote proxy option for clients that need localhost · OAuth 2.1 for Jira, Confluence, and Compass; API tokens required for Jira Service Management and Bitbucket, and optional elsewhere for headless setups · Apache-2.0 · 1,008★
- Atlassian Cloud only — no Jira Server or Data Center support
- Rate limits are tied to your Atlassian plan tier and enforced server-side; users report hitting 429s well below the documented ~1,000 requests/hour ceiling (open GitHub issue #171)
- Jira Service Management and Bitbucket tools require API-token auth rather than OAuth
- Lower GitHub adoption (1,008 stars) than the leading community server, though stars matter less for a hosted service
- Community
Teams on Jira Server or Data Center, and anyone who wants self-hosted control with the most-adopted community server
The broadest documented tool surface of any Jira MCP server — the README cites 98 tools covering JQL search, issue create/update, status transitions, and comments, plus Confluence CQL search and page editing; works with Jira Cloud and Jira Server/Data Center 8.14+
Self-hosted — run locally or on your infrastructure via Docker, uvx, or pip; supports SSE and streamable-http transports and multi-user setups · API tokens (Cloud), Personal Access Tokens (Server/Data Center), or OAuth 2.0; credentials stay in your own environment · MIT · 5,820★
- Not an official Atlassian product — the repo says so explicitly
- Self-hosted: you run the container or process and manage the credentials yourself
- OAuth 2.0 setup for Cloud is more involved than plain API-token auth
- Community
Teams that want a hosted endpoint with managed auth across many apps — Jira plus everything else — without running servers
Create, update, comment on, and search Jira issues, manage sprints, and assign work, per Composio's toolkit docs; one endpoint also reaches 1,000+ other managed integrations, with documented setup guides for Cursor, Claude Code, and Codex
Fully hosted by Composio — each team gets a secure MCP endpoint with tool-level controls and an audit trail; SOC 2 Type 2 certified · Managed Atlassian OAuth handled by Composio — you authorize once and Composio holds and refreshes the tokens
- A third party sits between your agent and Jira — your OAuth grant and traffic go through Composio's infrastructure
- Free to start, but paid usage tiers apply as volume grows
- Built around Atlassian Cloud OAuth; not a route to Server/Data Center
- Community
Non-technical teams already on Zapier who want scoped Jira actions in an AI client with zero setup
Exposes Zapier's predefined Jira Software Cloud actions (create, update, find issues) to any MCP client, with the ability to scope exactly which actions are available; separate MCP servers exist for Jira Service Management and Jira Software Server
Fully hosted by Zapier; you generate an endpoint and pick which Jira actions the AI is allowed to call · Zapier-managed connection with built-in authentication on the MCP endpoint — no OAuth apps or config files on your side
- Task-metered billing: one MCP tool call consumes 2 tasks from your Zapier plan quota, which gets expensive for chatty agents
- Limited to Zapier's predefined action catalog, not the full Jira API surface
- Jira Cloud, Server, and JSM are split across separate Zapier MCP servers — pick the right one
- Community
Developers who want a minimal, Jira-only binary with no Confluence baggage and no container runtime
Jira-only coverage per its README: issue management, sprint planning, and workflow transitions, aimed at AI assistants like Claude
Self-hosted — a single Go binary you run locally · Atlassian API token, configured via environment variables · MIT · 97★
- Small adoption — 97 stars against sooperset's 5,820
- Slower maintenance: last pushed April 18, 2026, over four months before our check
- Unofficial, and no Confluence support if you need it later
Jira MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Atlassian Remote MCP Server (official) | Atlassian | Fully hosted by Atlassian at mcp.atlassian.com — no install; connect via the remote URL, with an mcp-remote proxy option for clients that need localhost | OAuth 2.1 for Jira, Confluence, and Compass; API tokens required for Jira Service Management and Bitbucket, and optional elsewhere for headless setups | Apache-2.0 |
| sooperset/mcp-atlassian | Community | Self-hosted — run locally or on your infrastructure via Docker, uvx, or pip; supports SSE and streamable-http transports and multi-user setups | API tokens (Cloud), Personal Access Tokens (Server/Data Center), or OAuth 2.0; credentials stay in your own environment | MIT |
| Composio Jira MCP | Community | Fully hosted by Composio — each team gets a secure MCP endpoint with tool-level controls and an audit trail; SOC 2 Type 2 certified | Managed Atlassian OAuth handled by Composio — you authorize once and Composio holds and refreshes the tokens | — |
| Zapier Jira Software Cloud MCP | Community | Fully hosted by Zapier; you generate an endpoint and pick which Jira actions the AI is allowed to call | Zapier-managed connection with built-in authentication on the MCP endpoint — no OAuth apps or config files on your side | — |
| nguyenvanduocit/jira-mcp | Community | Self-hosted — a single Go binary you run locally | Atlassian API token, configured via environment variables | MIT |
How to choose
Pick the official Atlassian server if you are on Jira Cloud and want OAuth with nothing to host — just know the rate limits are tied to your Atlassian plan tier. Pick sooperset/mcp-atlassian if you run Jira Server or Data Center, want the larger community tool surface, or want credentials to stay on your own machine. Pick Composio if you want a hosted endpoint with managed OAuth across many apps, not just Jira. Pick Zapier if you already pay for Zapier and want scoped, no-code Jira actions — accepting task-metered billing. The Go server is for people who want one small Jira-only binary.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official MCP server for Jira?
- Yes. Atlassian ships the Atlassian Remote MCP Server, hosted at mcp.atlassian.com and generally available. It covers Jira, Confluence, Jira Service Management, Bitbucket, and Compass — but only for Atlassian Cloud sites.
- What does setup and authentication actually look like?
- On Jira Cloud, the official server uses an OAuth 2.1 browser consent flow, with API tokens as the option for headless setups (and a requirement for JSM and Bitbucket tools). On Jira Server or Data Center there is no official option — the standard route is self-hosting sooperset/mcp-atlassian with a Personal Access Token.
- Do these servers work with Cursor?
- Yes. The official Atlassian server documents one-click Cursor setup alongside Claude, ChatGPT, and VS Code, and sooperset/mcp-atlassian runs as a local process you add in Cursor's MCP settings. Composio also publishes a Cursor-specific setup guide for its hosted Jira endpoint.
- What if I'm on Jira Server or Data Center?
- The official server won't help — it is Cloud-only. sooperset/mcp-atlassian supports Jira Server/Data Center 8.14+ using Personal Access Tokens, and is the only actively maintained server on this list that does.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.