20 Best Jira MCP Servers, Compared (September 2026)
The short answer
Most readers should reach for MCP Atlassian (sooperset/mcp-atlassian). It is the community favourite for Atlassian Cloud, had a commit 2 days ago, and logged 159 commits in the last 12 weeks, so it is the most active Atlassian Cloud integration. If you need self-hosted Jira and Bitbucket, atlassian-mcp (stubbedev/atlassian-mcp) is the better answer: it exposes 10 tools for tickets, pull requests, and git context, and had a commit 1 day 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 : Teams using Atlassian Cloud who need to search, create, update, and transition Jira issues and manage Confluence pages via MCP.
- 2Atlassian Rovo MCP Server : Atlassian Cloud teams whose AI assistants need live Jira and Confluence context: this is Atlassian's official remote MCP server, backed by the Teamwork Graph.
- 3Atlassian Bitbucket MCP Server : Managing Bitbucket repositories and pull requests from an AI assistant: it exposes create, read, update, delete, and clone tools.
- 4Atlassian Data Center MCP : Teams using Atlassian Data Center (Jira, Confluence, Bitbucket) who want MCP access with scriptable setup and secure token storage.
- 5Atlassian Confluence MCP Server : Read-write AI access to a Confluence wiki: it exposes five generic tools covering get, post, put, patch, and delete on any API endpoint.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I use Atlassian Cloud for Jira and Confluence | MCP Atlassian (sooperset/mcp-atlassian) is the fit: it is a community favourite, had a commit 2 days ago, and logged 159 commits in the last 12 weeks. |
| I run Atlassian Data Center and need Jira, Confluence, and Bitbucket | Atlassian Data Center MCP (b1ff/atlassian-dc-mcp) is the fit: it targets Data Center products and had 66 commits in the last 12 weeks. |
| I need self-hosted Jira and Bitbucket in one server | atlassian-mcp (stubbedev/atlassian-mcp) is the fit: it exposes 10 tools for tickets, pull requests, and git context, and had a commit 1 day ago. |
| I operate Jira Service Management alerts and on-call schedules | jira-alerts-mcp is the fit: it exposes 13 tools for alerts and on-call lookups, and had a commit 1 day ago. |
| I need Tempo worklog time tracking from Jira | Tempo MCP Server is the fit: it exposes seven tools for worklog retrieval, creation, bulk creation, editing, deletion, missing-day detection, and analytics. |
| I want a full Jira issue server for Claude Desktop | mcp-jira-stdio is the fit: it exposes 23 tools covering create, update, comment, search, and metadata lookup, and its tool descriptions are graded A. |
Top MCP servers for Jira
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Teams using Atlassian Cloud who need to search, create, update, and transition Jira issues and manage Confluence pages via MCP. | Community favourite | 5,856 | +156 | 2 days ago | 90.7 | |
| 2 | Atlassian Cloud teams whose AI assistants need live Jira and Confluence context: this is Atlassian's official remote MCP server, backed by the Teamwork Graph. | Community favourite | 1,013 | +77 | 3 days ago | 83.0 | |
| 3 | Managing Bitbucket repositories and pull requests from an AI assistant: it exposes create, read, update, delete, and clone tools. | Abandoned but popular | 161 | +1 | 185 days ago | 70.4 | |
| 4 | Teams using Atlassian Data Center (Jira, Confluence, Bitbucket) who want MCP access with scriptable setup and secure token storage. | Emerging | 93 | +10 | 4 days ago | 60.0 | |
| 5 | Read-write AI access to a Confluence wiki: it exposes five generic tools covering get, post, put, patch, and delete on any API endpoint. | Abandoned but popular | 61 | +1 | 278 days ago | 55.5 | |
| 6 | Managing Jira projects and issues via generic REST calls: it exposes get, post, put, patch and delete tools for any endpoint. | Abandoned but popular | 73 | +1 | 185 days ago | 54.4 | |
| 7 | Full Jira issue management from Claude Desktop: it exposes 23 tools covering create, update, comment, search, and metadata lookup. | Steady | 14 | -1 | 3 days ago | 47.4 | |
| 8 | AI agents that need to manage kanban tasks, boards, and columns in the kanban-tui terminal task manager. | Community favourite | 280 | +12 | 9 days ago | 43.6 | |
| 9 | Self-hosted Jira with PAT auth: exposes 12 tools for issue CRUD, JQL search, comments, and assignment. | Abandoned but popular | 11 | +2 | 222 days ago | 42.0 | |
| 10 | Automating Jira issue management from an MCP client: it exposes tools for creating, updating, commenting on, and time-logging tasks. | Steady | 2 | +1 | today | 41.8 | |
| 11 | Managing Jira time tracking: it exposes seven tools covering worklog retrieval, creation, bulk creation, editing, deletion, missing-day detection, and analytics. | Steady | 45 | +3 | 65 days ago | 40.3 | |
| 12 | AI assistants that work with Jira and Confluence: it exposes search, read, create, update, and delete tools for issues, pages, and more. | Steady | 27 | 0 | 24 days ago | 38.5 | |
| 13 | Teams that want to delegate Jira project and issue management to an AI assistant through natural language prompts. | Dormant | 63 | 0 | 363 days ago | 36.6 | |
| 14 | Mixed Confluence environments (Cloud plus on-premise Server/Data Center): one MCP server covers all, exposing tools for spaces, pages, search, comments, and attachments. | Steady | 5 | +3 | 4 days ago | 36.3 | |
| 15 | AI assistants that need to act on already-authenticated web apps (Slack, Discord, GitHub, Jira): it routes API calls through the user's logged-in browser session. | Community favourite | 933 | +47 | 41 days ago | 35.2 | |
| 16 | Working with Jira and Confluence from an MCP client: it exposes tools for searching, reading, creating, updating, and commenting on pages and issues, with Markdown-to-ADF conversion. | Dormant | 2 | 0 | 100 days ago | 34.3 | |
| 17 | For teams on self-hosted Jira and Bitbucket: it exposes tools for ticket, pull request, git context, and attachment workflows in one server. | Steady | 1 | 0 | yesterday | 33.8 | |
| 18 | Operating Jira Service Management alerts day to day: it exposes tools to search, read, acknowledge, close and annotate alerts, plus on-call schedule lookups. | Steady | 4 | No snapshot history | yesterday | 32.6 | |
| 19 | Automating Jira Cloud issue and sprint workflows: it exposes tools for creating, updating, transitioning, and analyzing issues and sprints. | Steady | 4 | 0 | 6 days ago | 32.3 | |
| 20 | AI coding tools searching content already stored in Qdrant: it adds semantic search and document relationship analysis over those vectorized collections. | Steady | 51 | +4 | 48 days ago | 32.2 |
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: Teams using Atlassian Cloud who need to search, create, update, and transition Jira issues and manage Confluence pages via MCP.
It exposes MCP tools for searching, creating, updating, and transitioning Jira issues, as well as searching, creating, updating, and adding comments to Confluence pages. It only supports Atlassian Cloud, not Server or Data Center deployments.
GitHub stars5,856Stars / 30 days+156npm / typical weekShips no npm packageTools exposednever inspectedLast commit2 days agoCommits / 12 weeks159Maintenance gradeATool descriptionsNot gradedScore 90.7: 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
- Momentum75 / 100 · weight 14%
- Stars gained, relative to size66
- Stars gained, absolute89
- 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.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 90.7
Best for: Atlassian Cloud teams whose AI assistants need live Jira and Confluence context: this is Atlassian's official remote MCP server, backed by the Teamwork Graph.
This is a remote MCP server hosted by Atlassian that connects AI assistants to live data in Jira, Confluence, Jira Service Management, Bitbucket, and Compass through the Teamwork Graph. It requires Atlassian Cloud hosting and authentication with OAuth 2.1 or an API token.
GitHub stars1,013Stars / 30 days+77npm / typical weekShips no npm packageTools exposednever inspectedLast commit3 days agoCommits / 12 weeks45Maintenance 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
- Momentum91 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute76
- 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
Best for: Managing Bitbucket repositories and pull requests from an AI assistant: it exposes create, read, update, delete, and clone tools.
The server exposes six tools, bb_get, bb_post, bb_put, bb_patch, bb_delete, and bb_clone, for reading and modifying Bitbucket resources. It requires Node.js 18 or higher and a Bitbucket Cloud account, and it does not support Bitbucket Server or Data Center.
GitHub stars161Stars / 30 days+1npm / typical week3.7KTools exposed6Last commit185 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsAScore 70.4: 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
- Momentum33 / 100 · weight 14%
- Stars gained, relative to size25
- Stars gained, absolute14
- npm download trend70
- 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
- 70.4
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 70.4
Best for: Teams using Atlassian Data Center (Jira, Confluence, Bitbucket) who want MCP access with scriptable setup and secure token storage.
This server provides MCP integration for Atlassian Data Center products, with setup commands that store credentials in the OS keychain or a local file. It requires an existing Atlassian Data Center instance and an API token.
GitHub stars93Stars / 30 days+10npm / typical weekShips no npm packageTools exposednever inspectedLast commit4 days agoCommits / 12 weeks66Maintenance gradeATool descriptionsNot gradedScore 60.0: show every number behind it
- Adoption49 / 100 · weight 40%
- GitHub stars49
- 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
- Momentum67 / 100 · weight 14%
- Stars gained, relative to size84
- Stars gained, absolute42
- 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.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 60.0
Best for: Read-write AI access to a Confluence wiki: it exposes five generic tools covering get, post, put, patch, and delete on any API endpoint.
The server exposes five tools (conf_get, conf_post, conf_put, conf_patch, conf_delete) that wrap any Confluence API endpoint, with optional jq filtering and a TOON output format. Before choosing it, note that it requires Atlassian site name, user email, and API token supplied via environment variables or a config file.
GitHub stars61Stars / 30 days+1npm / typical week6.1KTools exposed5Last commit278 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 55.5: 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 196 days ago, which counts every ref; the stored date would have published 196 days ago
- Repository maintenance grade55
- Commit cadence5
- Momentum34 / 100 · weight 14%
- Stars gained, relative to size31
- Stars gained, absolute14
- npm download trend65
- 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
- 65.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 55.5
Best for: Managing Jira projects and issues via generic REST calls: it exposes get, post, put, patch and delete tools for any endpoint.
The server exposes generic tools that map to the Jira REST API, covering get, post, put, patch and delete operations on any endpoint. It depends on ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL and ATLASSIAN_API_TOKEN environment variables for authentication.
GitHub stars73Stars / 30 days+1npm / typical week13.3KTools exposednever inspectedLast commit185 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 54.4: 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
- Momentum29 / 100 · weight 14%
- Stars gained, relative to size29
- Stars gained, absolute13
- npm download trend46
- 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.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 54.4
Best for: Full Jira issue management from Claude Desktop: it exposes 23 tools covering create, update, comment, search, and metadata lookup.
It is a stdio-based MCP server that wraps the Jira REST API, exposing tools for projects, issues, comments, users, and metadata. Before choosing it, note that it requires Node.js 20 and Jira credentials (base URL, email, API token) configured as environment variables.
GitHub stars14Stars / 30 days-1npm / typical week483Tools exposed23Last commit3 days agoCommits / 12 weeks27Maintenance gradeATool descriptionsAScore 47.4: 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
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum8 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend34
- 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
- 67.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 47.4
Best for: AI agents that need to manage kanban tasks, boards, and columns in the kanban-tui terminal task manager.
The server exposes MCP commands for managing tasks, boards, and columns in kanban-tui. It relies on kanban-tui's backends, which include sqlite, jira, and claude.
GitHub stars280Stars / 30 days+12npm / typical weekShips no npm packageTools exposednever inspectedLast commit9 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 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
- 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: Self-hosted Jira with PAT auth: exposes 12 tools for issue CRUD, JQL search, comments, and assignment.
It exposes 12 tools covering issue CRUD, JQL search, comments, assignment, and project/issue-type lookups. It requires JIRA_BASE_URL and JIRA_PAT environment variables, and assumes a self-hosted Jira instance with PAT authentication.
GitHub stars11Stars / 30 days+2npm / typical week480Tools exposed12Last commit222 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 42.0: show every number behind it
- Adoption56 / 100 · weight 40%
- GitHub stars27
- npm downloads52downloads 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
- Momentum45 / 100 · weight 14%
- Stars gained, relative to size50
- Stars gained, absolute21
- npm download trend64
- 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
- 60.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 42.0
Best for: Automating Jira issue management from an MCP client: it exposes tools for creating, updating, commenting on, and time-logging tasks.
This server exposes MCP tools that sync Jira tasks to a local cache, update their fields and statuses, add comments, and log time. It requires a Jira API token and configuration via the jira-mcp CLI before any tool can connect to an instance.
GitHub stars2Stars / 30 days+1npm / typical week35Tools exposednever inspectedLast committodayCommits / 12 weeks19Maintenance gradeATool descriptionsNot gradedScore 41.8: 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
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum36 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute15
- npm download trend56
- 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
- 59.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 41.8
Best for: Managing Jira time tracking: it exposes seven tools covering worklog retrieval, creation, bulk creation, editing, deletion, missing-day detection, and analytics.
The server exposes seven tools: retrieving worklogs in a date range, creating and bulk creating worklogs, editing or deleting entries, finding workdays with below-expected logged time, and aggregating worklogs by group. Before choosing it, note that it requires a Tempo API token, a Jira Cloud instance, and either a Jira API token or OAuth 2.0 PKCE authentication.
GitHub stars45Stars / 30 days+3npm / typical week140Tools exposed7Last commit65 days agoCommits / 12 weeks4Maintenance gradeBTool descriptionsCScore 40.3: 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
- Momentum58 / 100 · weight 14%
- Stars gained, relative to size55
- Stars gained, absolute26
- npm download trend100
- 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
- 60.8
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 40.3
- 12
Best for: AI assistants that work with Jira and Confluence: it exposes search, read, create, update, and delete tools for issues, pages, and more.
It exposes tools for searching, retrieving, creating, updating, and deleting Jira issues and Confluence pages, and its README documents Bitbucket and Xray for Jira support. Before choosing it, note that Xray for Jira is supported only on Server/Data Center deployments, not Cloud.
GitHub stars27Stars / 30 days0npm / typical weekShips no npm packageTools exposed71Last commit24 days agoCommits / 12 weeks24Maintenance 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: Teams that want to delegate Jira project and issue management to an AI assistant through natural language prompts.
This server exposes MCP tools for retrieving, creating, updating, and deleting Jira issues, along with user and issue type lookups. It requires a Jira host and either a basic auth email/token or a personal access token configured as environment variables.
GitHub stars63Stars / 30 days0npm / typical weekdownloads not countedTools exposednever inspectedLast commit363 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 36.6: 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
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- 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
- 43.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 36.6
Best for: Mixed Confluence environments (Cloud plus on-premise Server/Data Center): one MCP server covers all, exposing tools for spaces, pages, search, comments, and attachments.
It exposes MCP tools for Confluence spaces, pages, search, labels, comments, attachments, versions, watchers, permissions, tasks, and page export. Before choosing it, note that it defaults to read-only mode, so mutating tools stay disabled unless CONFLUENCE_READ_ONLY=false is set.
GitHub stars5Stars / 30 days+3npm / typical week613Tools exposed28Last commit4 days agoCommits / 12 weeks51Maintenance gradeATool descriptionsBScore 36.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
- Momentum37 / 100 · weight 14%
- Stars gained, relative to size53
- Stars gained, absolute22
- npm download trend24
- 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
- 66.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 36.3
Best for: AI assistants that need to act on already-authenticated web apps (Slack, Discord, GitHub, Jira): it routes API calls through the user's logged-in browser session.
The server exposes 42 tools for browser control and plugin-based web app access, all through a Chrome extension bridged to a local MCP server. Before choosing it, note that it requires Node.js 22+ and Chrome, and every tool remains off until explicitly enabled.
GitHub stars933Stars / 30 days+47npm / typical weekShips no npm packageTools exposed42Last commit41 days agoCommits / 12 weeks56Maintenance gradeATool descriptionsAScore 35.2: 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
- Momentum79 / 100 · weight 14%
- Stars gained, relative to size86
- Stars gained, absolute68
- 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
- 83.8
- × relevance: the keyword is mentioned here
- 0.42
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 35.2
Best for: Working with Jira and Confluence from an MCP client: it exposes tools for searching, reading, creating, updating, and commenting on pages and issues, with Markdown-to-ADF conversion.
The server exposes tools that search, read, create, update, and comment on Jira and Confluence content, converting Markdown to Atlassian Document Format. It requires an Atlassian URL, email, and API token, and it deliberately omits delete operations.
GitHub stars2Stars / 30 days0npm / typical week49Tools exposednever inspectedLast commit100 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 34.3: 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
- Momentum9 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend36
- 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.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 34.3
- 17
Best for: For teams on self-hosted Jira and Bitbucket: it exposes tools for ticket, pull request, git context, and attachment workflows in one server.
It exposes tools to search and mutate Jira issues, manage Bitbucket pull requests, comments, and file access, and gather git context from a single server. It requires self-hosted Jira and Bitbucket; cloud instances are explicitly not supported.
GitHub stars1Stars / 30 days0npm / typical week172Tools exposed10Last commityesterdayCommits / 12 weeks63Maintenance gradeATool descriptionsAScore 33.8: 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
- Momentum25 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend100
- Tool quality88 / 100 · weight 13%
- Tool description quality80
- 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
- 61.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 33.8
- 18
Best for: Operating Jira Service Management alerts day to day: it exposes tools to search, read, acknowledge, close and annotate alerts, plus on-call schedule lookups.
It exposes thirteen tools: alert search and detail, notes and activity logs, acknowledge, close, add note, add responder, request status, and on-call and schedule lookups. Writes are asynchronous, so after acknowledging or closing an alert you should check the request-status tool to confirm the action actually succeeded.
GitHub stars4Stars / 30 daysno snapshot historynpm / typical week0Tools exposed13Last commityesterdayCommits / 12 weeks38Maintenance gradeATool descriptionsAScore 32.6: 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
- Momentum44 / 100 · weight 14%
- Stars gained, relative to sizenot measuredno snapshot history yet
- Stars gained, absolutenot measuredno snapshot history yet
- npm download trend44
- Tool quality100 / 100 · weight 13%
- Tool description quality93
- 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.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 32.6
- 19
Best for: Automating Jira Cloud issue and sprint workflows: it exposes tools for creating, updating, transitioning, and analyzing issues and sprints.
This server exposes tools for managing Jira Cloud issues, filters, projects, boards, and sprints, plus batch operations and analysis via queue and analyze tools. It requires Jira Cloud credentials (email, API token, and host) to be provided as environment variables.
GitHub stars4Stars / 30 days0npm / typical week147Tools exposednever inspectedLast commit6 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
Best for: AI coding tools searching content already stored in Qdrant: it adds semantic search and document relationship analysis over those vectorized collections.
It is an MCP server that connects AI development tools to Qdrant and, per its README, exposes semantic search, hierarchy-aware search, attachment discovery, conflict detection, similarity, clustering, relationship analysis, and knowledge graphs. It assumes content is already vectorized in Qdrant; ingestion is handled by the separate qdrant-loader package.
GitHub stars51Stars / 30 days+4npm / typical weekShips no npm packageTools exposednever inspectedLast commit48 days agoCommits / 12 weeks72Maintenance gradeATool descriptionsNot gradedScore 32.2: 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
- 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 5 days ago, which counts every ref; the stored date would have published 5 days ago
- Repository maintenance grade100
- Commit cadence100
- Momentum44 / 100 · weight 14%
- Stars gained, relative to size55
- Stars gained, absolute27
- 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
- 63.1
- × relevance: the keyword is tagged here
- 0.60
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 32.2
Questions people ask
Does MCP Atlassian (sooperset/mcp-atlassian) work with Jira Server or Data Center?
No. It is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments. For Data Center, Atlassian Data Center MCP (b1ff/atlassian-dc-mcp) covers Jira, Confluence, and Bitbucket. For self-hosted Jira and Bitbucket, atlassian-mcp (stubbedev/atlassian-mcp) exposes 10 tools and had a commit 1 day ago.
How do I choose between MCP Atlassian and Atlassian Rovo MCP Server?
Both target Atlassian Cloud and both are labelled community favourites. MCP Atlassian had a commit 2 days ago and 159 commits in the last 12 weeks; Atlassian Rovo had a commit 3 days ago and 45 commits in the last 12 weeks. Rovo is the official remote server backed by the Teamwork Graph, while MCP Atlassian is the community integration with more commit activity.
What should I be careful about with aashari/mcp-server-atlassian-jira?
It exposes generic get, post, put, patch, and delete tools for any Jira REST API endpoint, so an agent has very broad access. It is labelled Abandoned but popular, the last commit was 185 days ago, and there are 0 commits in the last 12 weeks. Its npm package had 13,311 downloads in a typical week.
Which server should I use for Tempo time tracking?
Tempo MCP Server is built for Tempo worklogs and exposes seven tools covering retrieval, creation, bulk creation, editing, deletion, missing-day detection, and analytics. It is labelled Steady, had a commit 65 days ago, and its npm package had 140 downloads in a typical week. Its tool descriptions are graded C.
What does jira-alerts-mcp cover?
It covers Jira Service Management operations: searching alerts, reading notes and activity logs, acknowledging, closing, annotating, adding responders, and querying current and next on-call rotations. It exposes 13 tools, had a commit 1 day ago, and had 0 npm downloads in a typical week.
Which server should I use for full Jira issue management from Claude Desktop?
mcp-jira-stdio exposes 23 tools covering create, update, comment, search, and metadata lookup, and its tool descriptions are graded A. It is labelled Steady, had a commit 3 days ago, and had 27 commits in the last 12 weeks.