20 Best Jira MCP Servers, Compared (August 2026)
The short answer
Most readers should reach for MCP Atlassian (sooperset/mcp-atlassian). It carries the community-favourite badge, had a commit 0 days ago, 148 commits in the last 12 weeks, and 5,770 stars, and it puts Jira and Confluence tools side by side in a single install. If your Jira is on Atlassian Data Center instead of Atlassian Cloud, the better answer is Atlassian Data Center MCP (b1ff/atlassian-dc-mcp).
Whichever you choose, give it the narrowest access that still works — a read-only credential, a replica, a scratch account — and widen it only once you have watched what your agent actually asks for.
Glama operates the MCP registry these numbers are measured from, and sells MCP hosting and a gateway. No position on this page is paid for. How the registry is built.
Quick picks
- 1MCP Atlassian — Teams needing both Jira and Confluence from one MCP server, since it exposes Jira and Confluence tools side by side in a single install.
- 2Atlassian Rovo MCP Server — Teams on Atlassian Cloud who want Atlassian's own hosted MCP endpoint, with OAuth or API-token auth, for AI access to Jira data.
- 3Atlassian Bitbucket MCP Server — Managing Bitbucket Cloud PRs and code from an AI assistant — it ships write, delete, and clone-to-local tools, so it does not stop at reading data.
- 4Atlassian Data Center MCP — Self-hosted Atlassian Data Center teams needing MCP access to Jira, Confluence, and Bitbucket — it offers per-product setup CLIs with secure token storage.
- 5Atlassian Confluence MCP Server — Teams that need instant natural-language answers from Confluence — it exposes generic CRUD tools covering all Confluence API endpoints.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I use Atlassian Cloud and want Jira plus Confluence in one server. | Use MCP Atlassian (sooperset/mcp-atlassian) because it is the community favourite, had a commit 0 days ago and 148 commits in the last 12 weeks, and exposes Jira and Confluence in one install. |
| I host Atlassian Data Center and need Jira, Confluence, and Bitbucket. | Use Atlassian Data Center MCP (b1ff/atlassian-dc-mcp) because it is built for Data Center, offers per-product setup CLIs for Jira, Confluence, and Bitbucket, and had 43 commits in the last 12 weeks. |
| I run self-hosted Jira Server and need PAT-based CRUD. | Use MCP Jira Server (edrich13/mcp-jira-server) because it targets self-hosted Jira with PAT auth and exposes CRUD, JQL, comments, and project tools. |
| I need Atlassian's scoped API tokens and safer defaults. | Use mcp-jira-scoped (deepwired/mcp-jira) because it uses api.atlassian.com with modern scoped API tokens and provides read-only default and delete confirmation. |
| I use Claude Code and want ticket context plus Figma links. | Use Jira MCP Server (rui-branco/jira-mcp) because it fetches and searches Jira tickets, comments, and attachments and auto-exports linked Figma designs. |
| I need to manage Tempo worklogs from Claude or Cursor. | Use Tempo MCP Server (ivelin-web/tempo-mcp-server) because it exposes 7 tools for Tempo worklogs including create, bulk-create, edit, delete, missing-day, and analytics. |
Top MCP servers for Jira
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Teams needing both Jira and Confluence from one MCP server, since it exposes Jira and Confluence tools side by side in a single install. | Community favourite | 5,770 | +146 | today | 90.4 | |
| 2 | Teams on Atlassian Cloud who want Atlassian's own hosted MCP endpoint, with OAuth or API-token auth, for AI access to Jira data. | Community favourite | 961 | +103 | 23 days ago | 83.0 | |
| 3 | Managing Bitbucket Cloud PRs and code from an AI assistant — it ships write, delete, and clone-to-local tools, so it does not stop at reading data. | Abandoned but popular | 160 | +3 | 167 days ago | 72.0 | |
| 4 | Self-hosted Atlassian Data Center teams needing MCP access to Jira, Confluence, and Bitbucket — it offers per-product setup CLIs with secure token storage. | Steady | 86 | +4 | 25 days ago | 56.9 | |
| 5 | Teams that need instant natural-language answers from Confluence — it exposes generic CRUD tools covering all Confluence API endpoints. | Abandoned but popular | 60 | 0 | 260 days ago | 53.2 | |
| 6 | For teams wanting natural-language Jira issue management in Claude — generic REST API tools allow project queries, comments, transitions and search. | Abandoned but popular | 72 | 0 | 167 days ago | 52.7 | |
| 7 | Managing Jira issues and projects directly from Claude Desktop — it exposes tools for creating, updating, commenting, and transitioning issues. | Steady | 15 | +1 | 10 days ago | 51.1 | |
| 8 | Agile teams working in Jira Cloud — it exposes full sprint lifecycle (create, update, close, move issues) and Confluence page lookup. | Steady | 5 | 0 | 82 days ago | 44.9 | |
| 9 | AI agents that manage tasks in a Jira-connected kanban board — it exposes task, board, and column management commands. | Community favourite | 269 | +11 | 11 days ago | 42.5 | |
| 10 | Teams needing to comply with Atlassian's token deprecation — it uses modern scoped tokens with api.atlassian.com, not classic tokens. | Dormant | 3 | 0 | 141 days ago | 42.1 | |
| 11 | Self-hosted Jira teams needing a quick CRUD MCP server — it exposes issue create, read, update, delete, search, and comment tools via PAT. | Dormant | 10 | +1 | 205 days ago | 39.6 | |
| 12 | Managing recurring tasks across multiple Jira instances — it supports config-file bulk creation, monthly task templates, and transition-path status updates. | Steady | 1 | 0 | today | 39.2 | |
| 13 | For delegating a new Jira issue to the most relevant teammate — its documented create tool accepts an assignee and user lookup. | Dormant | 63 | +1 | 345 days ago | 39.1 | |
| 14 | Teams using both Jira and Confluence that need AI to search, create, update, and comment with native formatting — it converts Markdown to ADF. | Steady | 2 | 0 | 82 days ago | 38.9 | |
| 15 | Jira teams needing both Jira and Confluence in one MCP server—it exposes 71 tools for issues, sprints, attachments, and pages. | Steady | 27 | -1 | 6 days ago | 38.5 | |
| 16 | Managing Tempo worklogs in Jira through Claude or Cursor — it provides create, bulk-create, edit, delete, missing-day, and analytics tools. | Steady | 42 | +1 | 48 days ago | 38.4 | |
| 17 | Already-logged-in web apps like Jira — it exposes real API tools through the user's existing browser session, no API keys or OAuth needed. | Community favourite | 897 | +34 | 23 days ago | 34.6 | |
| 18 | For teams using Confluence Server or Data Center who need broad page, space, and content access—including CQL search and exports—from an AI assistant. | Steady | 3 | 0 | 2 days ago | 33.2 | |
| 19 | Teams whose Jira content is already vectorized into Qdrant and need semantic search and relationship analysis for AI tools — this server provides that via MCP. | Steady | 50 | +5 | 30 days ago | 33.0 | |
| 20 | Developers using Claude Code who need Jira ticket context with linked Figma designs — it auto-exports Figma URLs from tickets. | Steady | 2 | 0 | yesterday | 32.0 |
The ranking, with the evidence
Each position is a weighted mean of adoption (40%), maintenance (24%), momentum (14%), tool description quality (13%) and trust (9%), multiplied by three attenuators: how directly the server is about Jira — named for it, declaring it, tagged with it, or merely mentioning it — whether its repository is still moving, and how much independent evidence of adoption it has. Open the score on any entry to see every number, including the ones marked ≈, which were imputed from the median of the other candidates rather than measured. The maintenance grade on each entry is mostly issue responsiveness, release recency and open security alerts rather than commits, so a recent commit beside a low grade is two different measurements rather than a contradiction.
- Abandoned but popular — People use it, but its default branch has stopped moving. Fine to keep running, risky to adopt.
- Community favourite — Widely adopted and still actively maintained.
- Dormant — Neither changing nor widely adopted. Here because it still matches the search.
- Emerging — Small audience, growing quickly, maintained. The bet with the most upside.
- Steady — Maintained, modest audience, no surprises in either direction.
- 1sooperset/mcp-atlassian ↗
MCP Atlassian
Community favouriteBest for: Teams needing both Jira and Confluence from one MCP server, since it exposes Jira and Confluence tools side by side in a single install.
It runs as a single uvx server exposing Jira tools (search, get, create, update, transition) and Confluence tools (search, get page, create page, comment) via documented environment-variable configuration. Before choosing it, note that the package description says Atlassian Cloud only, while the README and compatibility table claim Server/Data Center support with a personal access token.
GitHub stars5,770Stars / 30 days+146npm / typical weekShips no npm packageTools exposednever inspectedLast committodayCommits / 12 weeks148Maintenance gradeATool descriptionsNot gradedScore 90.4 — show every number behind it
- Adoption94 / 100 · weight 40%
- GitHub stars94
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum74 / 100 · weight 14%
- Stars gained, relative to size65
- Stars gained, absolute87
- npm download trendnot measuredno npm download history
- Tool quality≈73 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 90.4
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 90.4
- 2atlassian/atlassian-mcp-server ↗
Atlassian Rovo MCP Server
Community favouriteBest for: Teams on Atlassian Cloud who want Atlassian's own hosted MCP endpoint, with OAuth or API-token auth, for AI access to Jira data.
This is Atlassian's official, generally available cloud-hosted MCP bridge for Jira, using OAuth 2.1 or API-token authentication. The tool list has never been inspected here, so you are adopting it without a verified inventory of what it can actually do.
GitHub stars961Stars / 30 days+103npm / typical weekShips no npm packageTools exposednever inspectedLast commit23 days agoCommits / 12 weeks35Maintenance gradeBTool descriptionsNot gradedScore 83.0 — show every number behind it
- Adoption75 / 100 · weight 40%
- GitHub stars75
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance95 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence100
- Momentum93 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute81
- npm download trendnot measuredno npm download history
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integrates100
- Weighted mean of the five
- 83.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 83.0
- 3aashari/mcp-server-atlassian-bitbucket ↗
Atlassian Bitbucket MCP Server
Abandoned but popularBest for: Managing Bitbucket Cloud PRs and code from an AI assistant — it ships write, delete, and clone-to-local tools, so it does not stop at reading data.
Exposes six tools — bb_get, bb_post, bb_put, bb_patch, bb_delete, and bb_clone — for reading and writing Bitbucket Cloud resources and cloning repositories to the local filesystem. Worth knowing before choosing it: it supports only Bitbucket Cloud (not Bitbucket Server/Data Center) and requires Node.js 18.0.0 or higher.
GitHub stars160Stars / 30 days+3npm / typical week3.5KTools exposed6Last commit167 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsAScore 72.0 — show every number behind it
- Adoption84 / 100 · weight 40%
- GitHub stars55
- npm downloads76
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance46 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade30
- Commit cadence5
- Momentum45 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute23
- npm download trend83
- Tool quality93 / 100 · weight 13%
- Tool description quality85
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 72.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 72.0
Best for: Self-hosted Atlassian Data Center teams needing MCP access to Jira, Confluence, and Bitbucket — it offers per-product setup CLIs with secure token storage.
The server provides MCP integration for Atlassian Data Center products, with README-documented setup commands for Jira, Confluence, and Bitbucket that validate credentials before saving them. It assumes an on-premises Data Center deployment and requires a personal API token for each product; it does not cover Atlassian Cloud.
GitHub stars86Stars / 30 days+4npm / typical weekShips no npm packageTools exposednever inspectedLast commit25 days agoCommits / 12 weeks43Maintenance gradeATool descriptionsNot gradedScore 56.9 — show every number behind it
- Adoption48 / 100 · weight 40%
- GitHub stars48
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum44 / 100 · weight 14%
- Stars gained, relative to size54
- Stars gained, absolute29
- npm download trendnot measuredno npm download history
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 66.9
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 56.9
- 5aashari/mcp-server-atlassian-confluence ↗
Atlassian Confluence MCP Server
Abandoned but popularBest for: Teams that need instant natural-language answers from Confluence — it exposes generic CRUD tools covering all Confluence API endpoints.
This server exposes five generic tools — conf_get, conf_post, conf_put, conf_patch, and conf_delete — that map to Confluence's REST API, with optional JMESPath filtering and a token-efficient TOON output format. Before choosing it, note that it requires an Atlassian API token and your site name, user email, and token must be set as environment variables or in a config file.
GitHub stars60Stars / 30 days0npm / typical week4.4KTools exposed5Last commit260 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 53.2 — show every number behind it
- Adoption76 / 100 · weight 40%
- GitHub stars45
- npm downloads70downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance38 / 100 · weight 24%
- Last commit touching this server42dated from the last commit on the default branch, re-read from GitHub at publication; github.com shows a push 179 days ago, which counts every ref; the stored date would have published 179 days ago
- Repository maintenance grade55
- Commit cadence5
- Momentum16 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend63
- Tool quality91 / 100 · weight 13%
- Tool description quality83
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 62.6
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 53.2
- 6aashari/mcp-server-atlassian-jira ↗
Atlassian Jira MCP Server
Abandoned but popularBest for: For teams wanting natural-language Jira issue management in Claude — generic REST API tools allow project queries, comments, transitions and search.
It exposes generic GET, POST, PUT, PATCH, and DELETE tools that call Jira REST API endpoints, with TOON output and JMESPath filtering for responses. Before choosing it, know that it requires an Atlassian API token and that users must supply Jira REST API paths, since the tools are generic wrappers rather than dedicated issue or comment functions.
GitHub stars72Stars / 30 days0npm / typical week11.6KTools exposednever inspectedLast commit167 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 52.7 — show every number behind it
- Adoption79 / 100 · weight 40%
- GitHub stars47
- npm downloads72downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance46 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade30
- Commit cadence5
- Momentum15 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend61
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 62.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 52.7
Best for: Managing Jira issues and projects directly from Claude Desktop — it exposes tools for creating, updating, commenting, and transitioning issues.
It exposes 23 tools for reading, writing, and managing Jira issues and projects, spanning search, comments, transitions, and attachments. Note that it requires Node.js v20 or higher and a Jira API token passed as environment variables.
GitHub stars15Stars / 30 days+1npm / typical week469Tools exposed23Last commit10 days agoCommits / 12 weeks22Maintenance gradeATool descriptionsAScore 51.1 — show every number behind it
- Adoption60 / 100 · weight 40%
- GitHub stars30
- npm downloads55downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum43 / 100 · weight 14%
- Stars gained, relative to size32
- Stars gained, absolute12
- npm download trend100
- Tool quality83 / 100 · weight 13%
- Tool description quality75
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 73.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — small audience
- 0.70
- Composite score
- 51.1
Best for: Agile teams working in Jira Cloud — it exposes full sprint lifecycle (create, update, close, move issues) and Confluence page lookup.
It exposes 24 tools for Jira issue, comment, transition, assignment, and sprint management, plus a Confluence page query. Setup requires a Jira Cloud host, email, and API token; the README documents no support for Jira Server or Data Center.
GitHub stars5Stars / 30 days0npm / typical week67Tools exposed24Last commit82 days agoCommits / 12 weeks3Maintenance gradeCTool descriptionsAScore 44.9 — show every number behind it
- Adoption42 / 100 · weight 40%
- GitHub stars19
- npm downloads39
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance70 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade55
- Commit cadence40
- Momentum3 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend13
- Tool quality76 / 100 · weight 13%
- Tool description quality68
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 52.8
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 44.9
- 9Zaloog/kanban-tui ↗
kanban-tui
Community favouriteBest for: AI agents that manage tasks in a Jira-connected kanban board — it exposes task, board, and column management commands.
The server exposes task, board, and column management commands for AI agents, as described in its README, which also documents a CLI interface. It requires the kanban-tui terminal application to be installed, and its Jira backend needs an API key.
GitHub stars269Stars / 30 days+11npm / typical weekShips no npm packageTools exposednever inspectedLast commit11 days agoCommits / 12 weeks4Maintenance gradeATool descriptionsNot gradedScore 42.5 — show every number behind it
- Adoption61 / 100 · weight 40%
- GitHub stars61
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance88 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence40
- Momentum57 / 100 · weight 14%
- Stars gained, relative to size67
- Stars gained, absolute43
- npm download trendnot measuredno npm download history
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 70.8
- × relevance — the keyword is tagged here
- 0.60
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 42.5
- 10
Best for: Teams needing to comply with Atlassian's token deprecation — it uses modern scoped tokens with api.atlassian.com, not classic tokens.
This server exposes tools like jira_get_issue, jira_search, jira_create_issue, and jira_delete_issue, and its README documents that read tools are the default, with write tools requiring explicit scopes. Before choosing it, note that it requires a scoped token with a scoped token, not a classic one, and it does not support admin operations like project creation or workflow changes.
GitHub stars3Stars / 30 days0npm / typical week60Tools exposednever inspectedLast commit141 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 42.1 — show every number behind it
- Adoption40 / 100 · weight 40%
- GitHub stars15
- npm downloads38
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance52 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade55
- Commit cadence5
- Momentum25 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend100
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 49.5
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 42.1
Best for: Self-hosted Jira teams needing a quick CRUD MCP server — it exposes issue create, read, update, delete, search, and comment tools via PAT.
MCP Jira Server exposes 12 tools for creating, reading, updating, deleting, searching, commenting on, assigning, and listing issues and projects, using Personal Access Token authentication for self-hosted Jira. It requires a self-hosted Jira instance and Node.js 18+, and behind reverse proxies you may need to set a custom User-Agent to keep API requests from redirecting to SSO.
GitHub stars10Stars / 30 days+1npm / typical week469Tools exposed12Last commit205 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 39.6 — show every number behind it
- Adoption55 / 100 · weight 40%
- GitHub stars26
- npm downloads51downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance52 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade55
- Commit cadence5
- Momentum23 / 100 · weight 14%
- Stars gained, relative to size31
- Stars gained, absolute12
- npm download trend24
- Tool quality76 / 100 · weight 13%
- Tool description quality68
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 56.6
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — small audience
- 0.70
- Composite score
- 39.6
- 12
Best for: Managing recurring tasks across multiple Jira instances — it supports config-file bulk creation, monthly task templates, and transition-path status updates.
It is an MCP server and CLI whose documented tools sync Jira tasks to a local cache, read them, update fields and status, comment, delete, reassign, and log time. The one thing to weigh is that it requires an Atlassian API token and an initialized configuration at
~/.softspark/jira-mcp.GitHub stars1Stars / 30 days0npm / typical week28Tools exposednever inspectedLast committodayCommits / 12 weeks21Maintenance gradeATool descriptionsNot gradedScore 39.2 — show every number behind it
- Adoption32 / 100 · weight 40%
- GitHub stars8
- npm downloads31
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum17 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend67
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 56.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — small audience
- 0.70
- Composite score
- 39.2
Best for: For delegating a new Jira issue to the most relevant teammate — its documented create tool accepts an assignee and user lookup.
It documents MCP tools to create, update, link, and delete Jira issues, and to look up users, issue types, and link types. It requires JIRA_HOST and JIRA_API_TOKEN; basic auth also needs JIRA_EMAIL, while PAT auth uses bearer.
GitHub stars63Stars / 30 days+1npm / typical weekdownloads not countedTools exposednever inspectedLast commit345 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 39.1 — show every number behind it
- Adoption45 / 100 · weight 40%
- GitHub stars45
- npm downloadsnot measurednpm publishes jira-server from cfdude/mcp-jira
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance32 / 100 · weight 24%
- Last commit touching this server42
- Repository maintenance grade30
- Commit cadence5
- Momentum21 / 100 · weight 14%
- Stars gained, relative to size27
- Stars gained, absolute11
- npm download trendnot measuredno npm download history
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 46.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 39.1
Best for: Teams using both Jira and Confluence that need AI to search, create, update, and comment with native formatting — it converts Markdown to ADF.
The README documents an MCP server with tools for searching, reading, creating, updating, and commenting on Jira and Confluence content, converting Markdown to ADF. Before choosing it, note that it requires Atlassian credentials (URL, email, API token) set in the environment.
GitHub stars2Stars / 30 days0npm / typical week49Tools exposednever inspectedLast commit82 days agoCommits / 12 weeks14Maintenance gradeATool descriptionsNot gradedScore 38.9 — show every number behind it
- Adoption38 / 100 · weight 40%
- GitHub stars12
- npm downloads36
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance90 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade100
- Commit cadence85
- Momentum9 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend37
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 55.6
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — small audience
- 0.70
- Composite score
- 38.9
Best for: Jira teams needing both Jira and Confluence in one MCP server—it exposes 71 tools for issues, sprints, attachments, and pages.
It exposes 71 tools, covering Jira issue search, create/update/delete, transitions, sprints, attachments, comments, and worklogs, plus Confluence search and page retrieval. One scope check: Bitbucket Cloud is marked Not Tested, and Xray for Jira is available only on Server/Data Center.
GitHub stars27Stars / 30 days-1npm / typical weekShips no npm packageTools exposed71Last commit6 days agoCommits / 12 weeks26Maintenance gradeATool descriptionsBScore 38.5 — show every number behind it
- Adoption36 / 100 · weight 40%
- GitHub stars36
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trendnot measuredno npm download history
- Tool quality63 / 100 · weight 13%
- Tool description quality55
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 55.0
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — small audience
- 0.70
- Composite score
- 38.5
Best for: Managing Tempo worklogs in Jira through Claude or Cursor — it provides create, bulk-create, edit, delete, missing-day, and analytics tools.
The server wraps Tempo's API and exposes seven tools for retrieving, creating, bulk-creating, editing, deleting, and analyzing worklogs, plus missing-day reporting. It assumes a Jira Cloud instance and Tempo API credentials, with OAuth 2.0 PKCE available as the Jira API token alternative.
GitHub stars42Stars / 30 days+1npm / typical week130Tools exposed7Last commit48 days agoCommits / 12 weeks4Maintenance gradeBTool descriptionsCScore 38.4 — show every number behind it
- Adoption51 / 100 · weight 40%
- GitHub stars41
- npm downloads45
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance76 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade80
- Commit cadence40
- Momentum40 / 100 · weight 14%
- Stars gained, relative to size32
- Stars gained, absolute14
- npm download trend83
- Tool quality36 / 100 · weight 13%
- Tool description quality28
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 57.9
- × relevance — the keyword is declared here
- 0.78
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 38.4
- 17opentabs-dev/opentabs ↗
OpenTabs
Community favouriteBest for: Already-logged-in web apps like Jira — it exposes real API tools through the user's existing browser session, no API keys or OAuth needed.
OpenTabs routes AI agent requests to web APIs through the user's logged-in Chrome session, exposing 42 built-in tools for browser actions like screenshots, clicking, typing, and network capture. Before choosing it, note that it requires Node.js 22+ and Chrome, and every tool stays off until explicitly enabled.
GitHub stars897Stars / 30 days+34npm / typical weekShips no npm packageTools exposed42Last commit23 days agoCommits / 12 weeks96Maintenance gradeATool descriptionsAScore 34.6 — show every number behind it
- Adoption74 / 100 · weight 40%
- GitHub stars74
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum69 / 100 · weight 14%
- Stars gained, relative to size74
- Stars gained, absolute62
- npm download trendnot measuredno npm download history
- Tool quality78 / 100 · weight 13%
- Tool description quality70
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 82.4
- × relevance — the keyword is mentioned here
- 0.42
- × continuity — actively changing
- 1.00
- × evidence — widely adopted
- 1.00
- Composite score
- 34.6
Best for: For teams using Confluence Server or Data Center who need broad page, space, and content access—including CQL search and exports—from an AI assistant.
This server exposes 28 tools for reading and managing Confluence spaces, pages, comments, attachments, versions, watchers, permissions, and export URLs across Cloud, Server, and Data Center. Note that mutating tools are disabled by default; you must set CONFLUENCE_READ_ONLY=false and explicitly enable destructive operations.
GitHub stars3Stars / 30 days0npm / typical week595Tools exposed28Last commit2 days agoCommits / 12 weeks56Maintenance gradeATool descriptionsBScore 33.2 — show every number behind it
- Adoption42 / 100 · weight 40%
- GitHub stars15
- npm downloads40downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum12 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend48
- Tool quality68 / 100 · weight 13%
- Tool description quality60
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 60.4
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — no meaningful evidence of adoption
- 0.55
- Composite score
- 33.2
Best for: Teams whose Jira content is already vectorized into Qdrant and need semantic search and relationship analysis for AI tools — this server provides that via MCP.
The README documents an MCP server that provides semantic search, hierarchy-aware search, attachment discovery, and conflict detection over Qdrant data. It assumes the Qdrant collection is already populated, because this server is the retrieval layer while the separate qdrant-loader package handles ingestion.
GitHub stars50Stars / 30 days+5npm / typical weekShips no npm packageTools exposednever inspectedLast commit30 days agoCommits / 12 weeks104Maintenance gradeBTool descriptionsNot gradedScore 33.0 — show every number behind it
- Adoption43 / 100 · weight 40%
- GitHub stars43
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance95 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence100
- Momentum53 / 100 · weight 14%
- Stars gained, relative to size67
- Stars gained, absolute32
- npm download trendnot measuredno npm download history
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 64.7
- × relevance — the keyword is tagged here
- 0.60
- × continuity — actively changing
- 1.00
- × evidence — modest but real audience
- 0.85
- Composite score
- 33.0
Best for: Developers using Claude Code who need Jira ticket context with linked Figma designs — it auto-exports Figma URLs from tickets.
It exposes tools to fetch complete ticket details, comments, and attachments, search with JQL, and retrieve the current user's info. It requires a Jira Cloud account and API token, and the Figma integration depends on the separate figma-mcp server being configured.
GitHub stars2Stars / 30 days0npm / typical week140Tools exposednever inspectedLast commityesterdayCommits / 12 weeks11Maintenance gradeATool descriptionsNot gradedScore 32.0 — show every number behind it
- Adoption39 / 100 · weight 40%
- GitHub stars12
- npm downloads37downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum15 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend59
- Tool quality≈65 / 100 · weight 13%
- Tool description quality≈65tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 58.2
- × relevance — the keyword is dedicated here
- 1.00
- × continuity — actively changing
- 1.00
- × evidence — no meaningful evidence of adoption
- 0.55
- Composite score
- 32.0
Questions people ask
Should I pick MCP Atlassian or Atlassian Rovo MCP Server?
MCP Atlassian is the community favourite with 5,770 stars, a commit 0 days ago, and 148 commits in the last 12 weeks. Atlassian Rovo MCP Server is Atlassian's hosted bridge and covers Jira, Confluence, Jira Service Management, Bitbucket, and Compass, with 961 stars and a commit 23 days ago. Choose MCP Atlassian for Jira and Confluence from one actively maintained community install; choose Rovo if you want Atlassian's hosted endpoint and the wider Atlassian product set.
Does MCP Atlassian work with Jira Server or Data Center?
No. MCP Atlassian is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments. For Data Center, use Atlassian Data Center MCP (b1ff/atlassian-dc-mcp); for self-hosted Jira Server with PAT auth, use MCP Jira Server (edrich13/mcp-jira-server).
The aashari Jira server is popular—is it still maintained?
It is labelled Abandoned but popular. Its last commit was 167 days ago, and it had 0 commits in the last 12 weeks, so it has not seen recent maintenance. It still gets 11,571 npm downloads in a typical week, which is why it remains popular, but do not expect fixes.
What auth does mcp-jira-scoped use?
It uses Atlassian's modern scoped API tokens with api.atlassian.com instead of classic tokens. It also has safety features like read-only default and delete confirmation. This is aimed at teams that need to comply with Atlassian's token deprecation.
Which server works for Tempo worklogs?
Tempo MCP Server (ivelin-web/tempo-mcp-server) manages Tempo worklogs in Jira from MCP clients like Claude and Cursor. It exposes 7 tools covering create, bulk-create, edit, delete, missing-day, and analytics. Its last commit was 48 days ago, and it had 4 commits in the last 12 weeks.