20 Best Jira MCP Servers, Compared (September 2026)
The short answer
Reach for MCP Atlassian (sooperset/mcp-atlassian) if you are on Atlassian Cloud. It is a community favourite, with 5,813 stars, 155 commits in the last 12 weeks, and a commit 2 days ago, and its stated purpose is JQL search, issue creation, updates, and status transitions. If your job is Tempo time tracking instead, Tempo MCP Server is the better answer because it exposes seven tools for retrieving, creating, editing, deleting and bulk-logging time.
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 : Jira teams on Atlassian Cloud that need an MCP server for JQL search, issue creation, updates, and status transitions.
- 2Atlassian Rovo MCP Server : Atlassian Cloud teams: official MCP server with OAuth 2.1 or API token auth for Jira, Confluence, Jira Service Management, Bitbucket, and Compass.
- 3Atlassian Bitbucket MCP Server : Automating Bitbucket workflows like pull request creation and repository cloning: it exposes create, read, update, delete, and clone tools.
- 4Atlassian Data Center MCP : Atlassian Data Center teams needing MCP for Jira, Confluence, or Bitbucket: the setup validates credentials and stores them securely per product.
- 5Atlassian Confluence MCP Server : Confluence-heavy organizations that want AI assistants to read, search, create, and update pages: it exposes five generic tools covering any Confluence API endpoint.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I use Atlassian Cloud and need Jira issue automation | Use MCP Atlassian (sooperset/mcp-atlassian) for JQL search, issue creation, updates, and status transitions. |
| I want one official Atlassian bridge for many products | Use Atlassian Rovo MCP Server for secure real-time access to Jira, Confluence, Jira Service Management, Bitbucket, and Compass with OAuth 2.1 or API token auth. |
| I need Tempo time tracking through natural language | Use Tempo MCP Server: it exposes seven tools for retrieving, creating, editing, deleting and bulk-logging time. |
| I run self-hosted Jira and Bitbucket ticket-to-PR workflows | Use atlassian-mcp (stubbedev/atlassian-mcp); it exposes start_work, get_dev_context, and complete_work to connect tickets, branches, and PRs. |
| I need Atlassian Data Center support for Jira, Confluence, Bitbucket | Use Atlassian Data Center MCP (b1ff/atlassian-dc-mcp); it validates credentials and stores them securely per product. |
Top MCP servers for Jira
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Jira teams on Atlassian Cloud that need an MCP server for JQL search, issue creation, updates, and status transitions. | Community favourite | 5,813 | +143 | 2 days ago | 90.4 | |
| 2 | Atlassian Cloud teams: official MCP server with OAuth 2.1 or API token auth for Jira, Confluence, Jira Service Management, Bitbucket, and Compass. | Community favourite | 999 | +75 | 6 days ago | 82.9 | |
| 3 | Automating Bitbucket workflows like pull request creation and repository cloning: it exposes create, read, update, delete, and clone tools. | Abandoned but popular | 160 | +3 | 178 days ago | 72.6 | |
| 4 | Atlassian Data Center teams needing MCP for Jira, Confluence, or Bitbucket: the setup validates credentials and stores them securely per product. | Steady | 93 | +8 | today | 59.2 | |
| 5 | Confluence-heavy organizations that want AI assistants to read, search, create, and update pages: it exposes five generic tools covering any Confluence API endpoint. | Abandoned but popular | 60 | 0 | 271 days ago | 53.3 | |
| 6 | Teams that need an AI assistant to read and update Jira issues directly: it exposes generic HTTP tools for any Jira REST API endpoint. | Abandoned but popular | 72 | 0 | 178 days ago | 52.8 | |
| 7 | Jira users who need to create, update, comment on, search, and transition issues from Claude Desktop: it exposes 23 tools for those workflows. | Steady | 14 | 0 | 20 days ago | 48.0 | |
| 8 | Teams managing Jira sprints and Confluence from an AI assistant: it exposes sprint lifecycle tools and a wiki query tool. | Steady | 5 | 0 | 93 days ago | 46.0 | |
| 9 | A Jira user who wants AI-agent control of a terminal kanban board: it exposes task, board, and column management commands. | Community favourite | 276 | +10 | 2 days ago | 43.0 | |
| 10 | Jira teams with Atlassian scoped API tokens: it authenticates through api.atlassian.com and defaults to read-only. | Dormant | 3 | 0 | 152 days ago | 42.6 | |
| 11 | Bulk monthly task creation across multiple Jira projects: it supports multi-instance routing and workflow status transitions in configured order. | Steady | 2 | +1 | 11 days ago | 41.3 | |
| 12 | Self-hosted Jira instances with PAT authentication: it covers issue CRUD, JQL search, comments, assignment, and deletion through the REST API. | Dormant | 10 | +1 | 215 days ago | 40.1 | |
| 13 | Jira teams using Claude Desktop who want to delegate project-management chores: it documents issue, subtask, link, and workflow operations over MCP. | Dormant | 63 | +1 | 356 days ago | 39.1 | |
| 14 | Jira teams that need to manage Tempo worklogs through natural language: it exposes seven tools for retrieving, creating, editing, deleting and bulk-logging time. | Steady | 43 | +1 | 58 days ago | 39.0 | |
| 15 | Mixed Atlassian estates (Jira, Confluence, Bitbucket, and Xray): it exposes 71 tools for issue, sprint, board, page, and test-result workflows. | Steady | 27 | -1 | 17 days ago | 38.5 | |
| 16 | Jira users logged into Chrome: its plugin for Jira calls web APIs through the authenticated browser session, no API keys. | Community favourite | 918 | +43 | 34 days ago | 35.0 | |
| 17 | Teams using Atlassian Cloud who need AI-assisted issue and page creation/update with Markdown formatting: it converts Markdown to ADF and covers both Jira and Confluence. | Dormant | 2 | 0 | 93 days ago | 34.5 | |
| 18 | Self-hosted Jira and Bitbucket teams chasing ticket-to-PR workflows: it exposes start_work, get_dev_context, and complete_work to connect tickets, branches, and PRs. | Steady | 1 | 0 | 4 days ago | 33.8 | |
| 19 | A team running Confluence Cloud plus on-premise Server or Data Center: this is the pick because one npx server supports all three deployment types. | Steady | 3 | 0 | 12 days ago | 33.6 | |
| 20 | When AI coding tools must search Jira content in Qdrant: the project ingests Jira Cloud and Data Center and exposes search via MCP. | Steady | 50 | +5 | 41 days ago | 33.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.
Best for: Jira teams on Atlassian Cloud that need an MCP server for JQL search, issue creation, updates, and status transitions.
It is an MCP server for Atlassian Jira and Confluence whose README documents tools for JQL search, issue retrieval, creation, updates, transitions, and Confluence search, pages, and comments. The project's own description says Cloud only, while the README claims Server/Data Center support, so confirm the deployment type before choosing it.
GitHub stars5,813Stars / 30 days+143npm / typical weekShips no npm packageTools exposednever inspectedLast commit2 days agoCommits / 12 weeks155Maintenance 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
- Momentum73 / 100 · weight 14%
- Stars gained, relative to size64
- 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
Best for: Atlassian Cloud teams: official MCP server with OAuth 2.1 or API token auth for Jira, Confluence, Jira Service Management, Bitbucket, and Compass.
The server is an official cloud-hosted MCP server for Atlassian Cloud, authenticating via OAuth 2.1 or API token and linking to documentation for Jira, Confluence, Jira Service Management, Bitbucket, and Compass. Its exposed tool list is not published in the repository, so check Atlassian's supported-tools documentation before choosing it.
GitHub stars999Stars / 30 days+75npm / typical weekShips no npm packageTools exposednever inspectedLast commit6 days agoCommits / 12 weeks40Maintenance gradeBTool descriptionsNot gradedScore 82.9: 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
- Momentum90 / 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
- 82.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 82.9
Best for: Automating Bitbucket workflows like pull request creation and repository cloning: it exposes create, read, update, delete, and clone tools.
It exposes six tools that wrap Bitbucket's REST API for reading and writing resources, plus a clone tool for local git operations. It requires a Bitbucket Cloud account and authentication via a scoped API token or a legacy app password that is deprecated.
GitHub stars160Stars / 30 days+3npm / typical week3.6KTools exposed6Last commit178 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsAScore 72.6: 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
- Momentum49 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute23
- npm download trend97
- 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.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 72.6
Best for: Atlassian Data Center teams needing MCP for Jira, Confluence, or Bitbucket: the setup validates credentials and stores them securely per product.
The README documents a community-maintained MCP server for Atlassian Data Center products, with per-product setup commands that validate host and token against the selected product before saving credentials. The one thing worth knowing before choosing it: no npm package is published, while the README's quick setup depends on npx commands.
GitHub stars93Stars / 30 days+8npm / typical weekShips no npm packageTools exposednever inspectedLast committodayCommits / 12 weeks66Maintenance gradeATool descriptionsNot gradedScore 59.2: 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
- Momentum61 / 100 · weight 14%
- Stars gained, relative to size76
- Stars gained, absolute39
- 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
- 69.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 59.2
Best for: Confluence-heavy organizations that want AI assistants to read, search, create, and update pages: it exposes five generic tools covering any Confluence API endpoint.
It exposes five tools (conf_get, conf_post, conf_put, conf_patch, conf_delete) that call any Confluence REST endpoint with optional jq filtering and toon or json output. Before choosing it, know that it requires Atlassian credentials: site name, user email, and API token.
GitHub stars60Stars / 30 days0npm / typical week5.8KTools exposed5Last commit271 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 53.3: 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 189 days ago, which counts every ref; the stored date would have published 189 days ago
- Repository maintenance grade55
- Commit cadence5
- Momentum17 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend66
- 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.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 53.3
Best for: Teams that need an AI assistant to read and update Jira issues directly: it exposes generic HTTP tools for any Jira REST API endpoint.
It connects AI assistants to Jira through jira_get, jira_post, jira_put, jira_patch, and jira_delete tools that can call any Jira REST API path. Before choosing it, note that it requires an Atlassian site name, user email, and API token.
GitHub stars72Stars / 30 days0npm / typical week13.1KTools exposednever inspectedLast commit178 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 52.8: 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
- Momentum16 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend63
- 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.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 52.8
Best for: Jira users who need to create, update, comment on, search, and transition issues from Claude Desktop: it exposes 23 tools for those workflows.
mcp-jira-stdio is a stdio MCP server that exposes 23 tools for Jira: issue creation and updates, comments, JQL search, attachments, transitions, and project metadata. Before choosing it, note the environment requirements: Node.js 20 or higher, a Jira instance, and a Jira API token passed via environment variables.
GitHub stars14Stars / 30 days0npm / typical week473Tools exposed23Last commit20 days agoCommits / 12 weeks22Maintenance gradeATool descriptionsAScore 48.0: 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
- Momentum14 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend57
- 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
- 68.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 48.0
Best for: Teams managing Jira sprints and Confluence from an AI assistant: it exposes sprint lifecycle tools and a wiki query tool.
The server exposes 24 tools for Jira issues, comments, transitions, users, sprints, and Confluence page lookup. One requirement to know before choosing it: the server expects a Jira Cloud host, email address, and API token in the MCP client configuration.
GitHub stars5Stars / 30 days0npm / typical week70Tools exposed24Last commit93 days agoCommits / 12 weeks3Maintenance gradeCTool descriptionsAScore 46.0: 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
- Momentum11 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend44
- 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
- 54.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 46.0
Best for: A Jira user who wants AI-agent control of a terminal kanban board: it exposes task, board, and column management commands.
The MCP server exposes task, board, and column management commands for kanban-tui, a terminal task manager whose README also documents a Jira backend connecting via API key and querying tasks with JQL. Before choosing it, know that the Jira backend requires an API key and defines columns by task transitions.
GitHub stars276Stars / 30 days+10npm / typical weekShips no npm packageTools exposednever inspectedLast commit2 days agoCommits / 12 weeks9Maintenance gradeATool descriptionsNot gradedScore 43.0: 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
- Momentum54 / 100 · weight 14%
- Stars gained, relative to size62
- Stars gained, absolute41
- 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
- 71.7
- × relevance: the keyword is tagged here
- 0.60
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 43.0
Best for: Jira teams with Atlassian scoped API tokens: it authenticates through api.atlassian.com and defaults to read-only.
mcp-jira-scoped exposes Jira read, write, and user tools such as jira_get_issue, jira_search, jira_create_issue, and jira_delete_issue, with setup documented through environment variables. It requires a scoped Atlassian API token with the ATATT prefix rather than a classic token.
GitHub stars3Stars / 30 days0npm / typical week70Tools exposednever inspectedLast commit152 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 42.6: show every number behind it
- Adoption42 / 100 · weight 40%
- GitHub stars15
- npm downloads39
- 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
- 50.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 42.6
Best for: Bulk monthly task creation across multiple Jira projects: it supports multi-instance routing and workflow status transitions in configured order.
The server's documented tools sync tasks to a local cache, update status by stepping through workflow transitions, convert markdown fields and comments to ADF, and log time entries. It requires an Atlassian API token and local configuration initialized with jira-mcp config init, set-credentials, and add-project before use.
GitHub stars2Stars / 30 days+1npm / typical week35Tools exposednever inspectedLast commit11 days agoCommits / 12 weeks22Maintenance gradeATool descriptionsNot gradedScore 41.3: 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
- Momentum31 / 100 · weight 14%
- Stars gained, relative to size36
- Stars gained, absolute13
- npm download trend44
- 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.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 41.3
Best for: Self-hosted Jira instances with PAT authentication: it covers issue CRUD, JQL search, comments, assignment, and deletion through the REST API.
The server exposes 12 tools for interacting with self-hosted Jira via a Personal Access Token, including issue CRUD, JQL search, comments, projects, assignment, and current user lookup. It requires a self-hosted Jira instance, a Personal Access Token, and Node.js 18 or higher.
GitHub stars10Stars / 30 days+1npm / typical week480Tools exposed12Last commit215 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 40.1: 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
- Momentum28 / 100 · weight 14%
- Stars gained, relative to size31
- Stars gained, absolute12
- npm download trend42
- 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
- 57.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 40.1
Best for: Jira teams using Claude Desktop who want to delegate project-management chores: it documents issue, subtask, link, and workflow operations over MCP.
The server connects Jira to MCP clients and its README documents tools for user lookup, issue types, link types, and issue creation, updates, deletion, and linking. Before choosing it, note that the server has not been inspected, so its actual tool list is unknown and README operations should be verified.
GitHub stars63Stars / 30 days+1npm / typical weekdownloads not countedTools exposednever inspectedLast commit356 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: Jira teams that need to manage Tempo worklogs through natural language: it exposes seven tools for retrieving, creating, editing, deleting and bulk-logging time.
The server exposes seven MCP tools that retrieve, create, edit, delete, bulk-create, and analyze Tempo worklogs, and it also reports working days whose logged time falls below the user's Tempo schedule. Before choosing it, note that it assumes Jira Cloud and requires a Tempo API token, plus a Jira API token unless OAuth 2.0 PKCE authentication is used.
GitHub stars43Stars / 30 days+1npm / typical week147Tools exposed7Last commit58 days agoCommits / 12 weeks4Maintenance gradeBTool descriptionsCScore 39.0: show every number behind it
- Adoption52 / 100 · weight 40%
- GitHub stars41
- 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
- Momentum43 / 100 · weight 14%
- Stars gained, relative to size30
- Stars gained, absolute13
- 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
- 58.8
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 39.0
Best for: Mixed Atlassian estates (Jira, Confluence, Bitbucket, and Xray): it exposes 71 tools for issue, sprint, board, page, and test-result workflows.
This server exposes 71 tools covering Jira issue, sprint, board, attachment, and Confluence page operations, including JQL search, transitions, worklogs, and page retrieval. The compatibility scope to know: Xray for Jira is only available on Server/Data Center, Bitbucket Cloud is listed as not tested, and Jira and Confluence are supported on both Cloud and Server/Data Center.
GitHub stars27Stars / 30 days-1npm / typical weekShips no npm packageTools exposed71Last commit17 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: Jira users logged into Chrome: its plugin for Jira calls web APIs through the authenticated browser session, no API keys.
OpenTabs is a local MCP server paired with a Chrome extension; its exposed tools cover browser actions and network inspection, and its plugin system supports services including Jira through the user's logged-in session. The requirement to weigh before installing: Node.js 22+, Chrome, a manually loaded extension, and per-tool enablement, since every tool starts disabled.
GitHub stars918Stars / 30 days+43npm / typical weekShips no npm packageTools exposed42Last commit34 days agoCommits / 12 weeks84Maintenance gradeATool descriptionsAScore 35.0: 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
- Momentum76 / 100 · weight 14%
- Stars gained, relative to size83
- Stars gained, absolute66
- 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.3
- × relevance: the keyword is mentioned here
- 0.42
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 35.0
Best for: Teams using Atlassian Cloud who need AI-assisted issue and page creation/update with Markdown formatting: it converts Markdown to ADF and covers both Jira and Confluence.
The server exposes Confluence search, page read/create/update, comment, version, and permission tools, along with Jira search, create, update, and comment operations. The notable constraint is that it requires Atlassian credentials (URL, email, API token) and intentionally has no delete operations.
GitHub stars2Stars / 30 days0npm / typical week49Tools exposednever inspectedLast commit93 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 34.5: 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
- Momentum11 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend44
- 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.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 34.5
- 18
Best for: Self-hosted Jira and Bitbucket teams chasing ticket-to-PR workflows: it exposes start_work, get_dev_context, and complete_work to connect tickets, branches, and PRs.
The server exposes natural-language tools that tie git context, Jira tickets, and Bitbucket pull requests together, with get_dev_context and start_work as workflow entry points. Before choosing it, note that it supports only self-hosted Jira and Bitbucket; Jira Cloud and Bitbucket Cloud are not supported.
GitHub stars1Stars / 30 days0npm / typical week161Tools exposed10Last commit4 days agoCommits / 12 weeks59Maintenance 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
Best for: A team running Confluence Cloud plus on-premise Server or Data Center: this is the pick because one npx server supports all three deployment types.
It exposes 28 tools for reading and searching Confluence content, covering spaces, pages by ID/title/URL, CQL search, labels, comments, attachments, page hierarchy, versions, watchers, permissions, recently modified pages, inline tasks, and PDF/Word export links. One thing worth knowing before choosing it: it assumes Node.js 18+ and a Confluence Cloud, Server, or Data Center instance, and by default its tools are read-only unless CONFLUENCE_READ_ONLY is set to false.
GitHub stars3Stars / 30 days0npm / typical week613Tools exposed28Last commit12 days agoCommits / 12 weeks50Maintenance gradeATool descriptionsBScore 33.6: 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
- Momentum16 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend65
- 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
- 61.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 33.6
Best for: When AI coding tools must search Jira content in Qdrant: the project ingests Jira Cloud and Data Center and exposes search via MCP.
The monorepo contains a data ingestion pipeline that collects Jira, Confluence, Git, docs, and local files into Qdrant, and an MCP server whose README lists semantic search, hierarchy-aware search, attachment discovery, conflict detection, document similarity, clustering, relationship analysis, and knowledge graphs. A thing to know before choosing it: it assumes a running Qdrant instance and configured LLM embeddings, and Jira content must be loaded by the separate qdrant-loader ingestion package before the MCP server can search it.
GitHub stars50Stars / 30 days+5npm / typical weekShips no npm packageTools exposednever inspectedLast commit41 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
Questions people ask
Which should I pick: MCP Atlassian or Atlassian Rovo MCP Server?
On Atlassian Cloud, MCP Atlassian (sooperset/mcp-atlassian) is the community favourite with 5,813 stars, 155 commits in the last 12 weeks, and a commit 2 days ago. Atlassian Rovo MCP Server is the official option and covers Jira, Confluence, Jira Service Management, Bitbucket, and Compass, with 999 stars and 40 commits in the last 12 weeks. Choose Rovo when you want one official bridge across those products; choose MCP Atlassian when your focus is Jira and Confluence with the larger community.
What do I need to run mcp-jira-scoped?
It uses Atlassian's modern scoped API tokens and authenticates through api.atlassian.com. It defaults to read-only and has delete confirmation, which is useful for safety. The project is dormant: last commit 152 days ago and 0 commits in the last 12 weeks.
Is aashari/mcp-server-atlassian-jira safe to use after 178 days without a commit?
The project is labelled Abandoned but popular, last commit 178 days ago, 0 commits in the last 12 weeks, yet it still had 13,069 npm downloads in a typical week. It is positioned for teams that need an AI assistant to read and update Jira issues directly through generic HTTP tools for any Jira REST API endpoint. Use it only if you can tolerate an unmaintained dependency.
What is the difference between Atlassian Data Center MCP and MCP Jira Server for self-hosted Jira?
Atlassian Data Center MCP (b1ff/atlassian-dc-mcp) targets Atlassian Data Center products including Jira, Confluence, and Bitbucket, validates credentials, and stores them securely per product; it had a commit 0 days ago and 66 commits in the last 12 weeks. MCP Jira Server (edrich13/mcp-jira-server) targets self-hosted Jira with Personal Access Token authentication and covers issue CRUD, JQL search, comments, assignment, and deletion; it last committed 215 days ago and has 0 commits in the last 12 weeks. Choose the first for an active Data Center setup, the second only if you specifically need PAT auth on a self-hosted instance and accept dormancy.
How does OpenTabs handle Jira authentication?
It connects through the user's authenticated browser session with a Chrome extension, so no API keys are needed. It talks directly to web app internal APIs and does not use screenshots or DOM scraping. OpenTabs exposed 42 tools.
Can I get both Jira and Confluence with Markdown formatting?
Jira & Confluence MCP Server (thamaraiselvam/mcp-jira-confluence) connects AI assistants to Jira and Confluence and converts Markdown to ADF. It is labelled Dormant: last commit 93 days ago and 0 commits in the last 12 weeks. If you want a more active multi-product server, mcp-atlassian (SharkyND/mcp-atlassian) exposes 71 tools for Jira, Confluence, Bitbucket, and Xray and had a commit 17 days ago and 26 commits in the last 12 weeks.