20 Best Jira MCP Servers, Compared (September 2026)
The short answer
Use MCP Atlassian (sooperset/mcp-atlassian). It is a Community favourite on Atlassian Cloud, it had a commit 0 days ago, and it has 5,896 GitHub stars and 158 commits in the last 12 weeks. It covers both Jira and Confluence, with documented tools for searching, creating, updating, and transitioning issues. If your deployment is self-hosted Atlassian Data Center, the better answer is Atlassian Data Center MCP (b1ff/atlassian-dc-mcp), which is designed for Jira, Confluence, and Bitbucket on Data Center and had a commit 12 days ago.
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 : Atlassian Cloud teams needing one MCP server for both Jira and Confluence: it documents tools for searching, creating, updating, and transitioning issues.
- 2Atlassian Rovo MCP Server : Teams standardized on Atlassian Cloud: this official Atlassian server provides secure, real-time access to Jira, Confluence, Bitbucket and Compass.
- 3Atlassian Bitbucket MCP Server : AI-assisted code review and repository management on Bitbucket Cloud: it exposes six tools covering get, post, put, patch, delete, and clone operations.
- 4Atlassian Data Center MCP : Self-hosted Atlassian Data Center teams needing Jira, Confluence, and Bitbucket MCP access: its setup CLI validates credentials before storing them.
- 5Atlassian Confluence MCP Server : Connecting an AI assistant to an existing Atlassian Confluence instance: it exposes five generic tools covering read and write access to any Confluence API endpoint.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I need one server for Jira and Confluence on Atlassian Cloud | Use MCP Atlassian (sooperset/mcp-atlassian): it is built for Atlassian Cloud, is a Community favourite, and had a commit 0 days ago with 158 commits in the last 12 weeks. |
| I want an Atlassian-maintained server for Cloud products | Use Atlassian Rovo MCP Server (atlassian/atlassian-mcp-server), the official Atlassian server for Jira, Confluence, Jira Service Management, Bitbucket, and Compass. |
| I run self-hosted Atlassian Data Center | Use Atlassian Data Center MCP (b1ff/atlassian-dc-mcp), which covers Jira, Confluence, and Bitbucket on Data Center and had a commit 12 days ago. |
| I need self-hosted Jira with PAT authentication | Use MCP Jira Server (edrich13/mcp-jira-server), which is built for PAT auth and exposes 12 tools; it has had 0 commits in the last 12 weeks, so account for that. |
| I need Tempo worklog tracking from an AI assistant | Use Tempo MCP Server (ivelin-web/tempo-mcp-server), which exposes 7 worklog tools including bulk create and is built for Claude and Cursor. |
| I triage Jira Service Management alerts and on-call | Use jira-alerts-mcp (rrvrs/jira-alerts-mcp), which searches alerts, reads notes and logs, acknowledges and closes alerts, and queries on-call rotations. |
Top MCP servers for Jira
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Atlassian Cloud teams needing one MCP server for both Jira and Confluence: it documents tools for searching, creating, updating, and transitioning issues. | Community favourite | 5,896 | +151 | today | 90.6 | |
| 2 | Teams standardized on Atlassian Cloud: this official Atlassian server provides secure, real-time access to Jira, Confluence, Bitbucket and Compass. | Community favourite | 1,033 | +77 | 5 days ago | 83.1 | |
| 3 | AI-assisted code review and repository management on Bitbucket Cloud: it exposes six tools covering get, post, put, patch, delete, and clone operations. | Abandoned but popular | 162 | +2 | 193 days ago | 68.5 | |
| 4 | Self-hosted Atlassian Data Center teams needing Jira, Confluence, and Bitbucket MCP access: its setup CLI validates credentials before storing them. | Emerging | 95 | +10 | 12 days ago | 59.9 | |
| 5 | Connecting an AI assistant to an existing Atlassian Confluence instance: it exposes five generic tools covering read and write access to any Confluence API endpoint. | Abandoned but popular | 61 | +1 | 286 days ago | 54.1 | |
| 6 | Teams that need natural-language access to arbitrary Jira REST API endpoints: it exposes generic get, post, put, patch, and delete tools. | Abandoned but popular | 74 | +2 | 193 days ago | 54.1 | |
| 7 | Bamboo CI/CD teams needing build logs and build triggering from an AI assistant: its log tools return actual log content and it can trigger builds. | Steady | 5 | +1 | 7 days ago | 49.9 | |
| 8 | Managing Jira issues end to end from Claude Desktop: it exposes create, update, comment, transition, link, and subtask tools. | Steady | 14 | -1 | today | 45.9 | |
| 9 | Jira users who want a terminal kanban with AI agents: its Jira backend connects via API key and queries tasks via JQL. | Community favourite | 283 | +12 | 17 days ago | 43.6 | |
| 10 | Multi-instance Jira teams: it routes requests across several Jira instances from one MCP server. | Steady | 2 | 0 | 5 days ago | 41.2 | |
| 11 | Self-hosted Jira with PAT authentication: it provides tools for issue CRUD, JQL search, comments, and project listing. | Abandoned but popular | 13 | +3 | 230 days ago | 41.2 | |
| 12 | Teams that need one MCP server for Jira and Confluence on Cloud or Data Center: it covers issue, sprint, worklog, attachment, and Confluence search tools. | Steady | 27 | 0 | today | 38.2 | |
| 13 | Jira administrators needing to migrate off classic API tokens: this server uses Atlassian's scoped tokens via the modern api.atlassian.com gateway, with a read-only default. | Dormant | 3 | 0 | 167 days ago | 38.1 | |
| 14 | Jira Tempo users who want natural-language worklog tracking from Claude or Cursor: it exposes seven worklog management tools, including bulk create. | Steady | 45 | +3 | 73 days ago | 37.6 | |
| 15 | Read-only access to Confluence Server and Data Center: it exposes 28 tools for reading pages, searching content, and exporting pages, and defaults to read-only mode. | Steady | 5 | +3 | 5 days ago | 35.3 | |
| 16 | Jira work in an already logged-in Chrome session: OpenTabs connects AI to web app internal APIs through a Chrome extension, no API keys needed. | Community favourite | 939 | +47 | 49 days ago | 34.6 | |
| 17 | AI-assisted teams needing both read and write across Jira and Confluence: it offers Markdown-to-ADF conversion for native-looking issues and pages. | Dormant | 2 | 0 | 108 days ago | 34.2 | |
| 18 | On-call teams triaging JSM Operations alerts from an agent: it searches alerts, reads notes/logs, acknowledges/closes, and queries on-call rotations. | Steady | 4 | +4 | 2 days ago | 32.5 | |
| 19 | Jira Cloud teams that want natural-language issue and sprint management: it exposes tools for issues, filters, projects, boards, sprints, and batch operations. | Steady | 4 | 0 | 14 days ago | 32.3 | |
| 20 | Self-hosted Jira and Bitbucket teams: start_work creates a branch from a ticket and complete_work merges the PR and transitions the ticket to Done. | Steady | 1 | 0 | today | 31.4 |
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.
Best for: Atlassian Cloud teams needing one MCP server for both Jira and Confluence: it documents tools for searching, creating, updating, and transitioning issues.
It is an MCP server that, per its README, provides tools for Jira and Confluence operations including search, read, create, update, and transition. Before choosing it, note that its own description limits support to Atlassian Cloud, conflicting with the README's claim of Server/Data Center support.
GitHub stars5,896Stars / 30 days+151npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast committodayCommits / 12 weeks158Maintenance gradeATool descriptionsNot gradedScore 90.6: 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, absolute88
- npm download trendnot measuredno download history for the selected registry
- 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.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 90.6
Best for: Teams standardized on Atlassian Cloud: this official Atlassian server provides secure, real-time access to Jira, Confluence, Bitbucket and Compass.
The README describes a cloud-hosted MCP server that uses OAuth 2.1 or an API token to connect AI tools to Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and the wider Atlassian platform. Before choosing it, note that it requires Atlassian Cloud hosting.
GitHub stars1,033Stars / 30 days+77npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit5 days agoCommits / 12 weeks50Maintenance gradeBTool descriptionsNot gradedScore 83.1: 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
- Momentum91 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute76
- npm download trendnot measuredno download history for the selected registry
- 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.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 83.1
Best for: AI-assisted code review and repository management on Bitbucket Cloud: it exposes six tools covering get, post, put, patch, delete, and clone operations.
The server exposes six tools for Bitbucket Cloud: bb_get, bb_post, bb_put, bb_patch, bb_delete, and bb_clone. Before choosing it, note that it requires Bitbucket Cloud, not Bitbucket Server/Data Center, and Node.js 18.0.0 or higher.
GitHub stars162Stars / 30 days+2npm / typical week3.6KPyPI / typical weekno attributed packageTools exposed6Last commit193 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsAScore 68.5: 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
- Momentum20 / 100 · weight 14%
- Stars gained, relative to size32
- Stars gained, absolute19
- npm download trend0
- 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
- 68.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 68.5
Best for: Self-hosted Atlassian Data Center teams needing Jira, Confluence, and Bitbucket MCP access: its setup CLI validates credentials before storing them.
The README describes MCP servers for Jira, Confluence, and Bitbucket Data Center, plus a setup command that checks host, API base path, and token with an authenticated request before saving them. At publication, no npm package was published and no PyPI package was attributed to it, so the documented npx commands rely on packages that were not observed.
GitHub stars95Stars / 30 days+10npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit12 days agoCommits / 12 weeks68Maintenance gradeATool descriptionsNot gradedScore 59.9: show every number behind it
- Adoption50 / 100 · weight 40%
- GitHub stars50
- 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
- Momentum66 / 100 · weight 14%
- Stars gained, relative to size83
- Stars gained, absolute41
- npm download trendnot measuredno download history for the selected registry
- 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.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 59.9
Best for: Connecting an AI assistant to an existing Atlassian Confluence instance: it exposes five generic tools covering read and write access to any Confluence API endpoint.
The server exposes five tools, conf_get, conf_post, conf_put, conf_patch, and conf_delete, that call Confluence REST API endpoints directly with optional jq filtering and TOON output by default. The main requirement it imposes is an existing Confluence instance plus Atlassian site name, user email, and API token for authentication.
GitHub stars61Stars / 30 days+1npm / typical week6.3KPyPI / typical weekno attributed packageTools exposed5Last commit286 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 54.1: show every number behind it
- Adoption77 / 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 204 days ago, which counts every ref; the stored date would have published 204 days ago
- Repository maintenance grade55
- Commit cadence5
- Momentum23 / 100 · weight 14%
- Stars gained, relative to size31
- Stars gained, absolute14
- npm download trend17
- 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
- 63.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 54.1
Best for: Teams that need natural-language access to arbitrary Jira REST API endpoints: it exposes generic get, post, put, patch, and delete tools.
The server lets AI assistants call any Jira REST API endpoint through generic get, post, put, patch, and delete MCP tools. Before choosing it, note that it requires Atlassian credentials and offers generic API wrappers rather than purpose-built Jira tools.
GitHub stars74Stars / 30 days+2npm / typical week13.9KPyPI / typical weekno attributed packageTools exposednever inspectedLast commit193 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 54.1: 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
- Momentum26 / 100 · weight 14%
- Stars gained, relative to size37
- Stars gained, absolute18
- npm download trend14
- 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
- 63.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 54.1
Best for: Bamboo CI/CD teams needing build logs and build triggering from an AI assistant: its log tools return actual log content and it can trigger builds.
The server exposes 27 tools covering Bamboo server health, projects, plans, branches, build results and logs, and deployment projects, triggers, and results. It requires Node.js 18+ and a Bamboo personal access token, configured with the BAMBOO_URL and BAMBOO_TOKEN environment variables.
GitHub stars5Stars / 30 days+1npm / typical week105PyPI / typical weekno attributed packageTools exposed27Last commit7 days agoCommits / 12 weeks2Maintenance gradeBTool descriptionsBScore 49.9: show every number behind it
- Adoption46 / 100 · weight 40%
- GitHub stars19
- npm downloads43
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance83 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence40
- Momentum21 / 100 · weight 14%
- Stars gained, relative to size37
- Stars gained, absolute14
- npm download trend0
- Tool quality66 / 100 · weight 13%
- Tool description quality57
- 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
- 58.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 49.9
- 8
Best for: Managing Jira issues end to end from Claude Desktop: it exposes create, update, comment, transition, link, and subtask tools.
It connects a Jira instance to MCP clients over stdio and exposes tools for reading projects and issues, searching with JQL, and creating, updating, commenting on, transitioning, linking, and attaching to issues. Before choosing it, note that it requires Node.js 20 or higher, a Jira instance, and a Jira API token.
GitHub stars14Stars / 30 days-1npm / typical week483PyPI / typical weekno attributed packageTools exposed23Last committodayCommits / 12 weeks21Maintenance gradeBTool descriptionsAScore 45.9: show every number behind it
- Adoption59 / 100 · weight 40%
- GitHub stars29
- npm downloads54downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance92 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence85
- Momentum1 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend4
- 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
- 65.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 45.9
Best for: Jira users who want a terminal kanban with AI agents: its Jira backend connects via API key and queries tasks via JQL.
It is an MCP server for a Textual terminal task manager, exposing task, board, and column management commands for AI agents; the README documents sqlite, jira, and claude backends. Before choosing it, note that the server has never been inspected, so the exact tools it exposes are not measured.
GitHub stars283Stars / 30 days+12npm / typical weekShips no npm packagePyPI / typical weekdownloads not countedkanban-tuiTools exposednever inspectedLast commit17 days agoCommits / 12 weeks8Maintenance gradeATool descriptionsNot gradedScore 43.6: 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
- Maintenance93 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence65
- Momentum60 / 100 · weight 14%
- Stars gained, relative to size70
- Stars gained, absolute45
- npm download trendnot measuredno download history for the selected registry
- 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
- 72.7
- × relevance: the keyword is tagged here
- 0.60
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 43.6
Best for: Multi-instance Jira teams: it routes requests across several Jira instances from one MCP server.
The README documents Jira operations for sync, search, comments, transitions, time logging, reassignment, and creating and deleting issues. It targets Atlassian Cloud and expects one API token and a config directory at ~/.softspark/jira-mcp/.
GitHub stars2Stars / 30 days0npm / typical week35PyPI / typical weekno attributed packageTools exposednever inspectedLast commit5 days agoCommits / 12 weeks44Maintenance gradeATool descriptionsNot gradedScore 41.2: show every number behind it
- Adoption35 / 100 · weight 40%
- GitHub stars12
- npm downloads33
- 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
- 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
- 58.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 41.2
Best for: Self-hosted Jira with PAT authentication: it provides tools for issue CRUD, JQL search, comments, and project listing.
It exposes 12 tools covering issue CRUD, JQL search, comments, project listing, and assignment, all authenticated via PAT. It requires a self-hosted Jira instance and a Personal Access Token, so it cannot be used with Jira Cloud.
GitHub stars13Stars / 30 days+3npm / typical week473PyPI / typical weekno attributed packageTools exposed12Last commit230 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 41.2: show every number behind it
- Adoption58 / 100 · weight 40%
- GitHub stars29
- npm downloads54downloads 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
- Momentum31 / 100 · weight 14%
- Stars gained, relative to size54
- Stars gained, absolute23
- npm download trend0
- 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
- 58.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 41.2
Best for: Teams that need one MCP server for Jira and Confluence on Cloud or Data Center: it covers issue, sprint, worklog, attachment, and Confluence search tools.
It exposes 72 tools, mostly Jira operations (issue search, create, update, transitions, sprints, boards, worklogs, attachments, project versions) plus Confluence search. The one thing worth knowing before choosing it is that Xray for Jira is supported only on Server/Data Center, not Cloud.
GitHub stars27Stars / 30 days0npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed72Last committodayCommits / 12 weeks24Maintenance gradeATool descriptionsBScore 38.2: 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 download history for the selected registry
- Tool quality61 / 100 · weight 13%
- Tool description quality53
- 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
- 54.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 38.2
Best for: Jira administrators needing to migrate off classic API tokens: this server uses Atlassian's scoped tokens via the modern api.atlassian.com gateway, with a read-only default.
It exposes read tools such as jira_get_issue, jira_search, and jira_list_projects, plus write tools such as jira_create_issue, jira_update_issue, and jira_add_comment, with delete operations gated by a confirm parameter. Before installing, note the environment requirements: a scoped API token with ATATT prefix, JIRA_INSTANCE, JIRA_USER_EMAIL, and Node 18 or newer; if JIRA_SCOPES is omitted, only read tools are registered.
GitHub stars3Stars / 30 days0npm / typical week63PyPI / typical weekno attributed packageTools exposednever inspectedLast commit167 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 38.1: show every number behind it
- Adoption41 / 100 · weight 40%
- GitHub stars15
- npm downloads38
- 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
- Momentum1 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend3
- 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
- 44.8
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 38.1
Best for: Jira Tempo users who want natural-language worklog tracking from Claude or Cursor: it exposes seven worklog management tools, including bulk create.
The server exposes seven MCP tools for retrieving, creating, editing, deleting, and analyzing Tempo worklogs, and its README documents local npx, local clone, and Cloudflare Workers remote deployment. A requirement to note: it assumes a Jira Cloud instance, a Tempo API token, and, unless OAuth 2.0 PKCE is used, a Jira API token.
GitHub stars45Stars / 30 days+3npm / typical week140PyPI / typical weekno attributed packageTools exposed7Last commit73 days agoCommits / 12 weeks4Maintenance gradeBTool descriptionsCScore 37.6: show every number behind it
- Adoption52 / 100 · weight 40%
- GitHub stars42
- npm downloads46
- 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
- Momentum29 / 100 · weight 14%
- Stars gained, relative to size49
- Stars gained, absolute23
- npm download trend0
- 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
- 56.7
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 37.6
Best for: Read-only access to Confluence Server and Data Center: it exposes 28 tools for reading pages, searching content, and exporting pages, and defaults to read-only mode.
This Confluence MCP server exposes 28 tools for testing the connection, listing spaces and pages, running CQL and text searches, reading page bodies and metadata, and generating PDF/Word export URLs. It runs on Node.js 18+, and its read-only default keeps mutating tools disabled unless CONFLUENCE_READ_ONLY=false is set.
GitHub stars5Stars / 30 days+3npm / typical week588PyPI / typical weekno attributed packageTools exposed28Last commit5 days agoCommits / 12 weeks47Maintenance gradeATool descriptionsBScore 35.3: show every number behind it
- Adoption47 / 100 · weight 40%
- GitHub stars19
- npm downloads44downloads 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
- Momentum31 / 100 · weight 14%
- Stars gained, relative to size55
- Stars gained, absolute23
- npm download trend0
- Tool quality61 / 100 · weight 13%
- Tool description quality53
- 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
- 64.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 35.3
Best for: Jira work in an already logged-in Chrome session: OpenTabs connects AI to web app internal APIs through a Chrome extension, no API keys needed.
OpenTabs is an MCP server with a Chrome extension that exposes 42 tools for browser tab control, clicking and typing, network capture, and plugin checks. Before choosing it, note that it requires Node.js 22+ and Chrome, and every tool starts disabled until explicitly enabled.
GitHub stars939Stars / 30 days+47npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed42Last commit49 days agoCommits / 12 weeks39Maintenance 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
- Maintenance93 / 100 · weight 24%
- Last commit touching this server88dated from the last commit on the default branch, re-read from GitHub at publication; github.com shows a push 0 days ago, which counts every ref; the stored date would have published 3 days ago
- Repository maintenance grade100
- Commit cadence100
- Momentum79 / 100 · weight 14%
- Stars gained, relative to size86
- Stars gained, absolute68
- npm download trendnot measuredno download history for the selected registry
- 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: AI-assisted teams needing both read and write across Jira and Confluence: it offers Markdown-to-ADF conversion for native-looking issues and pages.
It exposes 15 tools that search Jira with JQL and Confluence with CQL, read and create issues and pages, update them, add comments, and perform Jira transitions. One thing to know before choosing it: it requires an Atlassian API token and deliberately includes no delete operations.
GitHub stars2Stars / 30 days0npm / typical week49PyPI / typical weekno attributed packageTools exposed15Last commit108 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 34.2: 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
- Maintenance63 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade55
- Commit cadence5
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend0
- Tool quality73 / 100 · weight 13%
- Tool description quality65
- 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
- 48.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 34.2
Best for: On-call teams triaging JSM Operations alerts from an agent: it searches alerts, reads notes/logs, acknowledges/closes, and queries on-call rotations.
jira-alerts-mcp exposes tools for working with Jira Service Management Operations alerts and on-call schedules, including alert search, detail and activity retrieval, acknowledgements, closes, notes, responders, and rotation lookups. Before choosing it, note that it requires Node 24 or newer, an Atlassian Cloud site with JSM Operations enabled, and an Atlassian API token passed through JSM_CLOUD_ID, JSM_EMAIL, and JSM_API_TOKEN.
GitHub stars4Stars / 30 days+4npm / typical week0PyPI / typical weekno attributed packageTools exposed28Last commit2 days agoCommits / 12 weeks46Maintenance gradeATool descriptionsAScore 32.5: show every number behind it
- Adoption17 / 100 · weight 40%
- GitHub stars17
- npm downloads0downloads show none of the weekday rhythm human traffic has; halved
- 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
- Momentum50 / 100 · weight 14%
- Stars gained, relative to size67
- Stars gained, absolute28
- npm download trend44
- 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
- 59.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 32.5
Best for: Jira Cloud teams that want natural-language issue and sprint management: it exposes tools for issues, filters, projects, boards, sprints, and batch operations.
The server wraps Jira Cloud APIs behind MCP tools for managing issues, filters, projects, boards, sprints, and queued batch operations, and also exposes resources such as instance summaries and custom-field catalogs. Before choosing it, note that it targets Jira Cloud only and needs an Atlassian API token plus the JIRA_EMAIL and JIRA_HOST environment variables.
GitHub stars4Stars / 30 days0npm / typical week140PyPI / typical weekno attributed packageTools exposednever inspectedLast commit14 days agoCommits / 12 weeks13Maintenance gradeATool descriptionsNot gradedScore 32.3: show every number behind it
- Adoption45 / 100 · weight 40%
- GitHub stars17
- npm downloads42downloads 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
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend0
- 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.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 32.3
- 20
Best for: Self-hosted Jira and Bitbucket teams: start_work creates a branch from a ticket and complete_work merges the PR and transitions the ticket to Done.
It exposes 10 tools for git context and Jira ticket workflows, and its README also documents Bitbucket pull request tools and a dev-context resource. Its scope is self-hosted instances only: the README explicitly says Jira Cloud and Bitbucket Cloud are not supported.
GitHub stars1Stars / 30 days0npm / typical week130PyPI / typical weekno attributed packageTools exposed10Last committodayCommits / 12 weeks69Maintenance gradeATool descriptionsAScore 31.4: show every number behind it
- Adoption34 / 100 · weight 40%
- GitHub stars8
- npm downloads33downloads 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
- Momentum1 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend4
- Tool quality81 / 100 · weight 13%
- Tool description quality73
- 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.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 31.4
Questions people ask
Which server should I choose for Atlassian Cloud: MCP Atlassian or Atlassian Rovo MCP Server?
MCP Atlassian (sooperset/mcp-atlassian) is a Community favourite with 5,896 GitHub stars, a commit 0 days ago, and 158 commits in the last 12 weeks. Atlassian Rovo MCP Server (atlassian/atlassian-mcp-server) is the official Atlassian server but has 1,033 GitHub stars, a commit 5 days ago, and 50 commits in the last 12 weeks. Pick MCP Atlassian for community activity and the documented Jira and Confluence tools; pick Rovo if being Atlassian-maintained matters more.
What should I use if I run Jira Data Center, not Cloud?
Atlassian Data Center MCP (b1ff/atlassian-dc-mcp) is designed for self-hosted Atlassian Data Center products including Jira, Confluence, and Bitbucket. It had a commit 12 days ago and 68 commits in the last 12 weeks. MCP Atlassian (sooperset/mcp-atlassian) is specifically for Atlassian Cloud, so it does not fit Data Center.
Is the abandoned aashari Jira server still worth using?
Atlassian Jira MCP Server (aashari/mcp-server-atlassian-jira) is labelled Abandoned but popular. Its last commit was 193 days ago, it had 0 commits in the last 12 weeks, and its npm package still saw 13,902 downloads in a typical week. That combination means you would be relying on code that is no longer being maintained, even though many others are using it.
What does jira-alerts-mcp actually cover?
jira-alerts-mcp (rrvrs/jira-alerts-mcp) covers Jira Service Management Operations alerts and on-call schedules. It can search alerts, read notes and activity logs, acknowledge, close, annotate, add responders, and query current and next on-call rotations. It exposes 28 tools and had a commit 2 days ago.
Does OpenTabs need a Jira API key?
OpenTabs does not need a Jira API key. It connects through a Chrome extension using the user's authenticated browser session, and its description says no API keys. It had a commit 49 days ago.
Which server is built for self-hosted Jira and Bitbucket together?
atlassian-mcp (stubbedev/atlassian-mcp) is for self-hosted Jira and Bitbucket. Its start_work tool creates a branch from a ticket and complete_work merges the PR and transitions the ticket to Done. It had a commit 0 days ago and 69 commits in the last 12 weeks.