20 Best Jira MCP Servers, Compared (October 2026)
The short answer
For most Jira Cloud readers, MCP Atlassian (sooperset/mcp-atlassian) is the one to install first: it is a Community favourite with 5,946 GitHub stars, 129 stars gained per 30 days, a commit 8 days ago, and 145 commits on its default branch in the last 12 weeks. Its README documents setup with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN for Claude Desktop and Cursor. If you are on self-hosted Jira and authenticate with a Personal Access Token, MCP Jira Server (edrich13/mcp-jira-server) is the better fit, with 12 tools for issue CRUD, JQL search, comments, projects, assignments, and current user lookup, though it had a last commit 243 days ago and 0 commits on its default branch in the last 12 weeks. For Jira Server or Data Center deployments that also need Confluence and Xray, mcp-atlassian (SharkyND/mcp-atlassian) is the alternative, with 72 issue, sprint, attachment, and Confluence search tools.
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 Cloud users needing an MCP server via uvx: the README documents setup with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN for Claude Desktop and Cursor.
- 2Atlassian Rovo MCP Server : Teams on Atlassian Cloud needing Jira, Confluence, and Jira Service Management access through a cloud-hosted MCP bridge with OAuth 2.1 or API token auth.
- 3Atlassian Bitbucket MCP Server : Bitbucket Cloud teams that need AI assistants to manage repositories and pull requests: it exposes six tools for get, post, put, patch, delete, and clone.
- 4Atlassian Data Center MCP : Atlassian Data Center deployments needing Jira, Confluence, and Bitbucket MCP access: the README documents per-product setup with credential validation and OS-specific token storage.
- 5Atlassian Jira MCP Server : Teams needing natural-language Jira issue management through Claude or Cursor: it exposes generic Jira REST API tools for reads, creates, updates, comments, transitions, and searches.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I use Jira Cloud and want the most established option. | MCP Atlassian (sooperset/mcp-atlassian) is a Community favourite with 5,946 GitHub stars, 129 stars gained per 30 days, a commit 8 days ago, and 145 commits on its default branch in the last 12 weeks. |
| I am on self-hosted Jira with a Personal Access Token. | MCP Jira Server (edrich13/mcp-jira-server) documents PAT authentication and exposes 12 tools for issue CRUD, JQL search, comments, projects, assignments, and current user lookup, though it had a last commit 243 days ago and 0 commits on its default branch in the last 12 weeks. |
| I need Jira Server or Data Center with Confluence and Xray. | mcp-atlassian (SharkyND/mcp-atlassian) documents Jira Server/Data Center, Confluence, and Xray support, exposes 72 issue, sprint, attachment, and Confluence search tools, and had a last commit 13 days ago with 24 commits on its default branch in the last 12 weeks. |
| I want scoped API tokens and read-only safety by default. | mcp-jira-scoped (deepwired/mcp-jira) enforces granted scopes server-side, restricts projects with JIRA_PROJECTS, defaults to read-only, and had a last commit 7 days ago with 19 commits on its default branch in the last 12 weeks. |
| I need to manage Tempo worklogs in Jira. | Tempo MCP Server (ivelin-web/tempo-mcp-server) exposes seven tools for retrieving, creating, bulk creating, editing, deleting worklogs, missing-day reports, and analytics, but its tool descriptions are graded C and it had 0 commits on its default branch in the last 12 weeks. |
| I want Jira access through an authenticated browser session. | OpenTabs (opentabs-dev/opentabs) calls Jira through the user's authenticated browser session via a Chrome extension and installed plugins, with no API keys, and exposes 42 tools. |
Top MCP servers for Jira
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Jira Cloud users needing an MCP server via uvx: the README documents setup with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN for Claude Desktop and Cursor. | Community favourite | 5,946 | +129 | 8 days ago | 90.0 | |
| 2 | Teams on Atlassian Cloud needing Jira, Confluence, and Jira Service Management access through a cloud-hosted MCP bridge with OAuth 2.1 or API token auth. | Community favourite | 1,062 | +70 | 12 days ago | 83.1 | |
| 3 | Bitbucket Cloud teams that need AI assistants to manage repositories and pull requests: it exposes six tools for get, post, put, patch, delete, and clone. | Abandoned but popular | 162 | +1 | 205 days ago | 70.7 | |
| 4 | Atlassian Data Center deployments needing Jira, Confluence, and Bitbucket MCP access: the README documents per-product setup with credential validation and OS-specific token storage. | Emerging | 100 | +10 | 5 days ago | 60.2 | |
| 5 | Teams needing natural-language Jira issue management through Claude or Cursor: it exposes generic Jira REST API tools for reads, creates, updates, comments, transitions, and searches. | Abandoned but popular | 77 | +6 | 205 days ago | 57.3 | |
| 6 | AI assistant access to Confluence knowledge bases: it exposes 5 generic tools for GET, POST, PUT, PATCH, and DELETE across Confluence API endpoints. | Abandoned but popular | 61 | 0 | 299 days ago | 53.1 | |
| 7 | Teams already running Bamboo CI/CD who troubleshoot builds from an editor: it reads build and deployment logs with actual content and can trigger builds. | Steady | 5 | +1 | 20 days ago | 53.1 | |
| 8 | Teams using Atlassian scoped API tokens for Jira: the server enforces granted scopes server-side, restricts projects with JIRA_PROJECTS, and defaults to read-only. | Steady | 4 | +1 | 7 days ago | 52.8 | |
| 9 | Claude Desktop users on Jira Cloud or Server who need issue creation, updates, comments, JQL search, and project management over stdio. | Steady | 14 | 0 | 13 days ago | 48.8 | |
| 10 | Jira Cloud teams needing multi-instance routing and comment templates: it documents project configuration, ADF formatting, and task caching. | Steady | 3 | +1 | 3 days ago | 43.6 | |
| 11 | Tracking Jira work as kanban columns: its Jira backend connects via API key, queries tasks with JQL, and defines columns by task transitions. | Community favourite | 284 | +6 | 30 days ago | 42.1 | |
| 12 | Self-hosted Jira instances using Personal Access Token authentication: it provides 12 tools for issue CRUD, JQL search, comments, projects, assignments, and current user lookup. | Abandoned but popular | 13 | +3 | 243 days ago | 40.7 | |
| 13 | Agile teams on Jira Cloud who need an AI client to manage sprints and issues: it exposes 24 tools including create_sprint, move_issue_to_sprint, transition_issue and create_comment. | Dormant | 5 | 0 | 121 days ago | 40.4 | |
| 14 | Querying Jira and Confluence offline: it mirrors selected projects and spaces into one local SQLite file that its MCP read tools answer from. | Steady | 42 | No snapshot history | today | 38.3 | |
| 15 | Jira Server/Data Center teams also needing Confluence and Xray: it documents support for those deployments and exposes 72 issue, sprint, attachment, and Confluence search tools. | Steady | 27 | 0 | 13 days ago | 38.2 | |
| 16 | Confluence Server or Data Center deployments: it exposes 28 tools for reading, searching, navigating, and exporting pages, including page bodies in chunks. | Steady | 5 | +3 | 4 days ago | 35.2 | |
| 17 | Jira and Confluence work through an MCP client: it exposes 37 tools for tickets, sprints, boards, worklogs, comments, attachments, users, and Confluence pages. | Steady | 1 | 0 | 38 days ago | 34.1 | |
| 18 | Teams already logged into Jira in Chrome: it calls Jira through the browser session via a Chrome extension and installed plugins, with no API keys. | Community favourite | 958 | +36 | 62 days ago | 33.8 | |
| 19 | For teams that want to query cloud and AI costs in plain English and file Jira tickets for waste, this local-first server fits. | Steady | 18 | +1 | today | 33.0 | |
| 20 | Managing Tempo worklogs in Jira: it exposes seven tools for retrieving, creating, bulk creating, editing, deleting worklogs, missing-day reports, and analytics. | Steady | 45 | 0 | 86 days ago | 32.7 |
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 Cloud users needing an MCP server via uvx: the README documents setup with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN for Claude Desktop and Cursor.
The README documents Jira tools for JQL search, issue retrieval, creation, update, and transition, plus Confluence tools for CQL search and page management, configured through environment variables. Its description states that it is designed specifically for Atlassian Cloud and does not support Atlassian Server or Data Center deployments.
GitHub stars5,946Stars / 30 days+129npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit8 days agoCommits / 12 weeks145Maintenance gradeATool descriptionsNot gradedScore 90.0: 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
- Momentum70 / 100 · weight 14%
- Stars gained, relative to size60
- Stars gained, absolute85
- 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.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 90.0
Best for: Teams on Atlassian Cloud needing Jira, Confluence, and Jira Service Management access through a cloud-hosted MCP bridge with OAuth 2.1 or API token auth.
The README documents a cloud-hosted MCP bridge that connects AI tools to Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom. One requirement worth knowing is that it assumes Atlassian Cloud hosting and authenticates via OAuth 2.1 or an API token.
GitHub stars1,062Stars / 30 days+70npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit12 days agoCommits / 12 weeks32Maintenance gradeBTool descriptionsNot gradedScore 83.1: show every number behind it
- Adoption76 / 100 · weight 40%
- GitHub stars76
- 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, absolute75
- 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: Bitbucket Cloud teams that need AI assistants to manage repositories and pull requests: it exposes six tools for get, post, put, patch, delete, and clone.
The Atlassian Bitbucket MCP Server connects MCP-compatible AI assistants to Bitbucket Cloud through six tools named bb_get, bb_post, bb_put, bb_patch, bb_delete, and bb_clone, and the README documents npx and configuration-file setup. It requires Node.js 18.0.0 or higher and a Bitbucket Cloud account with a scoped API token or app password, and it does not cover Bitbucket Server or Data Center.
GitHub stars162Stars / 30 days+1npm / typical week3.6KPyPI / typical weekno attributed packageTools exposed6Last commit205 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsAScore 70.7: 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
- Momentum35 / 100 · weight 14%
- Stars gained, relative to size28
- Stars gained, absolute16
- npm download trend73
- 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.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 70.7
Best for: Atlassian Data Center deployments needing Jira, Confluence, and Bitbucket MCP access: the README documents per-product setup with credential validation and OS-specific token storage.
The README documents per-product MCP setup for Jira, Confluence, and Bitbucket Data Center, including a setup subcommand that validates host, API base path, and API token and stores credentials in an OS-appropriate location. It assumes an Atlassian Data Center deployment with host and API token credentials, which the setup command validates and stores before the MCP server boots.
GitHub stars100Stars / 30 days+10npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit5 days agoCommits / 12 weeks60Maintenance gradeATool descriptionsNot gradedScore 60.2: 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, absolute42
- 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.8
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 60.2
Best for: Teams needing natural-language Jira issue management through Claude or Cursor: it exposes generic Jira REST API tools for reads, creates, updates, comments, transitions, and searches.
It connects AI assistants to Jira through MCP and documents generic HTTP-method tools for calling Jira REST API endpoints. Before choosing it, note that it requires an Atlassian site name, user email, and API token.
GitHub stars77Stars / 30 days+6npm / typical week14.4KPyPI / typical weekno attributed packageTools exposednever inspectedLast commit205 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsNot gradedScore 57.3: 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
- Momentum52 / 100 · weight 14%
- Stars gained, relative to size65
- Stars gained, absolute33
- npm download trend48
- 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
- 67.4
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 57.3
Best for: AI assistant access to Confluence knowledge bases: it exposes 5 generic tools for GET, POST, PUT, PATCH, and DELETE across Confluence API endpoints.
The server exposes 5 generic tools (conf_get, conf_post, conf_put, conf_patch, conf_delete) that call Confluence API paths with optional query parameters, JMESPath jq filtering, and TOON output by default. Before choosing it, know that it requires Atlassian site name, user email, and API token credentials and expects callers to supply Confluence API endpoint paths themselves.
GitHub stars61Stars / 30 days0npm / typical week6.3KPyPI / typical weekno attributed packageTools exposed5Last commit299 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 53.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 217 days ago, which counts every ref; the stored date would have published 217 days ago
- Repository maintenance grade55
- Commit cadence5
- Momentum14 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend58
- 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.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 53.1
Best for: Teams already running Bamboo CI/CD who troubleshoot builds from an editor: it reads build and deployment logs with actual content and can trigger builds.
The server exposes 27 tools spanning Bamboo server info and health checks, projects, plans and branches, build triggering and results, build and deployment queues, and deployment projects and results, including tools that fetch log content rather than log URLs. Before it can reach anything it needs BAMBOO_URL and a Bamboo personal access token supplied as environment variables, with an optional proxy setting for corporate networks.
GitHub stars5Stars / 30 days+1npm / typical week105PyPI / typical weekno attributed packageTools exposed27Last commit20 days agoCommits / 12 weeks2Maintenance gradeBTool descriptionsBScore 53.1: 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
- Momentum47 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute16
- npm download trend100
- 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
- 62.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 53.1
Best for: Teams using Atlassian scoped API tokens for Jira: the server enforces granted scopes server-side, restricts projects with JIRA_PROJECTS, and defaults to read-only.
The README documents a Jira MCP server that uses Atlassian scoped API tokens against the api.atlassian.com gateway, registers toolsets selected through JIRA_TOOLSETS, enforces JIRA_SCOPES before API calls, and can restrict access with a JIRA_PROJECTS allowlist. The main constraint is that it requires a scoped Jira API token and defaults to read-only unless write scopes are granted; Atlassian does not allow token scopes to be read back or edited after creation.
GitHub stars4Stars / 30 days+1npm / typical week63PyPI / typical weekno attributed packageTools exposednever inspectedLast commit7 days agoCommits / 12 weeks19Maintenance gradeATool descriptionsNot gradedScore 52.8: show every number behind it
- Adoption41 / 100 · weight 40%
- GitHub stars17
- npm downloads38
- 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
- Momentum35 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute15
- npm download trend54
- 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
- 9
Best for: Claude Desktop users on Jira Cloud or Server who need issue creation, updates, comments, JQL search, and project management over stdio.
mcp-jira-stdio is an npm-installed MCP server that exposes 23 Jira tools for retrieving projects and issues, running JQL searches, creating and updating issues, adding comments, managing attachments, and transitioning workflow statuses over stdio. Before choosing it, note that it requires Node.js v20 or higher and Jira credentials supplied through JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN.
GitHub stars14Stars / 30 days0npm / typical week508PyPI / typical weekno attributed packageTools exposed23Last commit13 days agoCommits / 12 weeks25Maintenance gradeATool descriptionsAScore 48.8: 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
- Momentum25 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend100
- 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
- 69.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 48.8
Best for: Jira Cloud teams needing multi-instance routing and comment templates: it documents project configuration, ADF formatting, and task caching.
The jira-mcp package is part of a two-server Atlassian Cloud setup, and its README documents Jira sync, search, comment, transition, log time, reassign, create, and delete operations alongside a companion Confluence server for pages, blog posts, comments, labels, attachments, restrictions, and whiteboards. Before choosing it, note that it requires npm global installation plus a shared Atlassian Cloud credential and configuration under ~/.softspark/jira-mcp/, and it is registered as its own MCP server separate from the Confluence server.
GitHub stars3Stars / 30 days+1npm / typical week42PyPI / typical weekno attributed packageTools exposednever inspectedLast commit3 days agoCommits / 12 weeks58Maintenance gradeATool descriptionsNot gradedScore 43.6: show every number behind it
- Adoption37 / 100 · weight 40%
- GitHub stars15
- npm downloads35
- 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 size33
- Stars gained, absolute12
- 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
- 62.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 43.6
Best for: Tracking Jira work as kanban columns: its Jira backend connects via API key, queries tasks with JQL, and defines columns by task transitions.
kanban-tui is a terminal task manager whose MCP server exposes task, board, and column management commands for AI agents, and whose README documents a CLI interface and a Jira backend that connects via API key and queries tasks with JQL. Its Jira backend requires an API key and defines columns by task transitions; the default backend is sqlite, and the MCP server's tool list has not been inspected.
GitHub stars284Stars / 30 days+6npm / typical weekShips no npm packagePyPI / typical weekdownloads not countedkanban-tuiTools exposednever inspectedLast commit30 days agoCommits / 12 weeks7Maintenance gradeATool descriptionsNot gradedScore 42.1: 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
- Momentum42 / 100 · weight 14%
- Stars gained, relative to size47
- Stars gained, absolute33
- 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.2
- × relevance: the keyword is tagged here
- 0.60
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 42.1
Best for: Self-hosted Jira instances using Personal Access Token authentication: it provides 12 tools for issue CRUD, JQL search, comments, projects, assignments, and current user lookup.
MCP Jira Server connects to a self-hosted Jira instance using Personal Access Token authentication and exposes 12 tools for retrieving and searching issues with JQL, creating, updating, assigning, and deleting issues, managing comments, and listing projects and issue types. Before choosing it, note that it requires a self-hosted Jira instance, a Personal Access Token, and Node.js 18 or higher.
GitHub stars13Stars / 30 days+3npm / typical week501PyPI / typical weekno attributed packageTools exposed12Last commit243 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsAScore 40.7: 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
- Maintenance38 / 100 · weight 24%
- Last commit touching this server42
- Repository maintenance grade55
- Commit cadence5
- Momentum51 / 100 · weight 14%
- Stars gained, relative to size54
- Stars gained, absolute24
- npm download trend77
- 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.1
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 40.7
Best for: Agile teams on Jira Cloud who need an AI client to manage sprints and issues: it exposes 24 tools including create_sprint, move_issue_to_sprint, transition_issue and create_comment.
It is an MCP server that exposes 24 tools across Jira issues, comments, transitions, assignments, users and the agile sprint lifecycle (boards, sprints, sprint issues), plus a Confluence page lookup by code. Setup assumes Jira Cloud credentials passed as JIRA_HOST, JIRA_EMAIL and JIRA_API_TOKEN, and the Confluence side only retrieves a page by its code rather than searching or editing pages.
GitHub stars5Stars / 30 days0npm / typical week70PyPI / typical weekno attributed packageTools exposed24Last commit121 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsAScore 40.4: 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
- Maintenance46 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade30
- Commit cadence5
- Momentum6 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend22
- 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
- 47.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 40.4
Best for: Querying Jira and Confluence offline: it mirrors selected projects and spaces into one local SQLite file that its MCP read tools answer from.
It mirrors selected Jira Cloud projects and Confluence spaces into a single local SQLite file and answers MCP reads from that file with read-only SQL, full-text search, issue detail, and sprint and retro reads. Before installing, note that it assumes an Atlassian API token, mirrors only the projects and spaces named at setup, and ships no Confluence Server client, so the wiki stays off on Jira Server and Data Center.
GitHub stars42Stars / 30 daysno snapshot historynpm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast committodayCommits / 12 weeks2,212Maintenance gradeATool descriptionsNot gradedScore 38.3: show every number behind it
- Adoption41 / 100 · weight 40%
- GitHub stars41
- 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
- Momentum≈0 / 100 · weight 14%
- Stars gained, relative to sizenot measuredno snapshot history yet
- Stars gained, absolutenot measuredno snapshot history yet
- 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
- 57.8
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 38.3
- 15
Best for: Jira Server/Data Center teams also needing Confluence and Xray: it documents support for those deployments and exposes 72 issue, sprint, attachment, and Confluence search tools.
mcp-atlassian is an MCP server for Atlassian products that exposes 72 tools, including Jira issue search, creation, updates, transitions, sprints, worklogs, attachments, and Confluence search, and its README documents Cloud and Server/Data Center support. Before choosing it, note that Xray for Jira is supported only on Server/Data Center and not on Cloud.
GitHub stars27Stars / 30 days0npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed72Last commit13 days agoCommits / 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: Confluence Server or Data Center deployments: it exposes 28 tools for reading, searching, navigating, and exporting pages, including page bodies in chunks.
Atlassian Confluence MCP Server is an open-source Model Context Protocol server exposing 28 tools for testing Confluence connections, listing and inspecting spaces, retrieving pages (including large bodies in chunks), searching with CQL or text, and reading labels, comments, attachments, hierarchy, versions, watchers, permissions, tasks, and export URLs. Before choosing it, note that it requires Node.js 22.12+ and environment-variable credentials for Cloud, Server, or Data Center, with read-only mode defaulting to true and mutating tools disabled unless changed.
GitHub stars5Stars / 30 days+3npm / typical week525PyPI / typical weekno attributed packageTools exposed28Last commit4 days agoCommits / 12 weeks43Maintenance gradeATool descriptionsBScore 35.2: 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
- Momentum30 / 100 · weight 14%
- Stars gained, relative to size52
- Stars gained, absolute22
- 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.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: no meaningful evidence of adoption
- 0.55
- Composite score
- 35.2
Best for: Jira and Confluence work through an MCP client: it exposes 37 tools for tickets, sprints, boards, worklogs, comments, attachments, users, and Confluence pages.
The server provides MCP tools for Jira and Confluence, including ticket creation and search, comment and attachment management, workflow transitions, field updates, worklogs, issue links, projects, versions, agile boards, sprints, users, and Confluence page retrieval and search. It requires Jira credentials through JIRA_HOST, JIRA_EMAIL, and JIRA_API_TOKEN, while its Confluence tools depend on separate CONFLUENCE_HOST, CONFLUENCE_EMAIL, and CONFLUENCE_API_TOKEN values.
GitHub stars1Stars / 30 days0npm / typical week25PyPI / typical weekno attributed packageTools exposed37Last commit38 days agoCommits / 12 weeks2Maintenance gradeCTool descriptionsBScore 34.1: show every number behind it
- Adoption31 / 100 · weight 40%
- GitHub stars8
- npm downloads30
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance77 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade55
- Commit cadence40
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend0
- 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
- 48.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 34.1
Best for: Teams already logged into Jira in Chrome: it calls Jira through the browser session via a Chrome extension and installed plugins, with no API keys.
OpenTabs runs a local MCP server beside a Chrome extension and exposes 42 tools, mostly browser controls for tabs, screenshots, clicking, typing, storage, and console and network capture, while Jira access comes from separately installed plugins that talk to a web app's internal APIs through the user's authenticated session instead of screenshots or DOM scraping. Choosing it means Chrome with an unpacked extension loaded manually from the local install, and the tools arrive disabled, so each one must be enabled and given a permission level before it will run.
GitHub stars958Stars / 30 days+36npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed42Last commit62 days agoCommits / 12 weeks15Maintenance gradeATool descriptionsAScore 33.8: 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
- Maintenance90 / 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 9 days ago, which counts every ref; the stored date would have published 9 days ago
- Repository maintenance grade100
- Commit cadence85
- Momentum70 / 100 · weight 14%
- Stars gained, relative to size74
- Stars gained, absolute63
- 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
- 80.5
- × relevance: the keyword is mentioned here
- 0.42
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 33.8
- 19
Best for: For teams that want to query cloud and AI costs in plain English and file Jira tickets for waste, this local-first server fits.
It exposes 10 MCP tools for connecting AWS, Azure, and GCP, summarizing spend, estimating change costs, checking AI budgets and action policies, and reporting setup status, while the README documents asking cost questions in plain English and opening Jira tickets for waste. Before choosing it, note that it is local-first: it reads credentials already on the machine, and Azure requires guided service-principal setup because nable cannot safely auto-detect local Azure credentials.
GitHub stars18Stars / 30 days+1npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed10Last committodayCommits / 12 weeks653Maintenance gradeATool descriptionsAScore 33.0: show every number behind it
- Adoption32 / 100 · weight 40%
- GitHub stars32
- 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
- Momentum28 / 100 · weight 14%
- Stars gained, relative to size37
- Stars gained, absolute15
- npm download trendnot measuredno download history for the selected registry
- 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
- 60.4
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 33.0
Best for: Managing Tempo worklogs in Jira: it exposes seven tools for retrieving, creating, bulk creating, editing, deleting worklogs, missing-day reports, and analytics.
The Tempo MCP Server manages Tempo worklogs in Jira through seven tools: retrieveWorklogs, createWorklog, bulkCreateWorklogs, editWorklog, deleteWorklog, getMissingWorklogDays, and getWorklogAnalytics, with usage documented for remote Cloudflare Workers, npx, or a local clone. It requires a Jira Cloud instance and Tempo API token (plus a Jira API token unless OAuth 2.0 PKCE authentication is used), and its remote setup stores credentials in a personal MCP URL.
GitHub stars45Stars / 30 days0npm / typical week130PyPI / typical weekno attributed packageTools exposed7Last commit86 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsCScore 32.7: show every number behind it
- Adoption51 / 100 · weight 40%
- GitHub stars42
- npm downloads45
- 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 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
- 49.3
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 32.7
Questions people ask
How do I choose between MCP Atlassian and Atlassian Rovo MCP Server?
MCP Atlassian (sooperset/mcp-atlassian) is for Atlassian Cloud and documents setup via uvx with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN for Claude Desktop and Cursor; it has 5,946 GitHub stars, 129 stars gained per 30 days, a last commit 8 days ago, and 145 commits on its default branch in the last 12 weeks. Atlassian Rovo MCP Server (atlassian/atlassian-mcp-server) is a cloud-hosted bridge for Jira, Confluence, Jira Service Management, Bitbucket, and Compass; it has 1,062 GitHub stars, 70 stars gained per 30 days, a last commit 12 days ago, and 32 commits on its default branch in the last 12 weeks. Choose MCP Atlassian for local Jira Cloud setup with those credentials, and choose Atlassian Rovo MCP Server if you want a cloud-hosted bridge across those Atlassian products.
What does MCP Atlassian require before it will run?
MCP Atlassian (sooperset/mcp-atlassian) is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments. Its README documents setup with JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN for Claude Desktop and Cursor. It is documented as a uvx setup for Jira Cloud users.
Which server should I use for self-hosted Jira with a Personal Access Token?
MCP Jira Server (edrich13/mcp-jira-server) is for self-hosted Jira instances using Personal Access Token authentication and provides 12 tools for issue CRUD, JQL search, comments, projects, assignments, and current user lookup. It is labeled Abandoned but popular, had a last commit 243 days ago, and had 0 commits on its default branch in the last 12 weeks, so weigh that inactivity. Atlassian Data Center MCP (b1ff/atlassian-dc-mcp) is another option for Atlassian Data Center products including Jira, Confluence, and Bitbucket, and it had a last commit 5 days ago with 60 commits on its default branch in the last 12 weeks.
What should I be careful about with abandoned but popular Jira servers?
Atlassian Jira MCP Server (aashari/mcp-server-atlassian-jira) is labeled Abandoned but popular, had a last commit 205 days ago, and had 0 commits on its default branch in the last 12 weeks. Its npm package had 14,375 downloads in a typical week. Atlassian Bitbucket MCP Server (aashari/mcp-server-atlassian-bitbucket) had a last commit 205 days ago and 0 commits on its default branch in the last 12 weeks, with 3,619 npm downloads in a typical week. High download counts do not by themselves show current maintenance.
Which server handles Tempo worklogs in Jira?
Tempo MCP Server (ivelin-web/tempo-mcp-server) manages Tempo worklogs in Jira and exposes seven tools for retrieving, creating, bulk creating, editing, deleting worklogs, missing-day reports, and analytics. Its tool descriptions are graded C, and it had a last commit 86 days ago and 0 commits on its default branch in the last 12 weeks. If worklog support must be actively maintained, that record is the main caution.
Can I use a Jira MCP server without API keys?
OpenTabs (opentabs-dev/opentabs) calls Jira through the user's authenticated browser session via a Chrome extension and installed plugins, with no API keys. It exposes 42 tools and is a Community favourite with 958 GitHub stars, 36 stars gained per 30 days, and a last commit 62 days ago. It had 15 commits on its default branch in the last 12 weeks.