20 Best Jira MCP Servers, Compared (November 2026)

The short answer

Which one, for your situation

Top MCP servers for Jira

The ranking, with the evidence

• 1

  MCP Atlassian

  Community favourite

  sooperset/mcp-atlassian ↗

  Best for: Teams running Jira and Confluence together on Atlassian Cloud: one server covers JQL issue search, issue creation and transitions, and Confluence page tools.

  It exposes Jira tools for JQL search, issue retrieval, creation, updates and status transitions, alongside Confluence tools for CQL search and page create/update, configured through environment variables such as JIRA_URL and JIRA_API_TOKEN. Its own description limits it to Atlassian Cloud and rules out Server and Data Center, while the README separately claims Server/Data Center support, so confirm which deployment you run before installing.

  Score 88.0: show every number behind it

  • Adoption95 / 100 · weight 40%
    • GitHub stars95
    • npm downloadsnot measured
      no npm package
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance92 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence85
  • Momentum68 / 100 · weight 14%
    • Stars gained, relative to size58
    • Stars gained, absolute84
    • npm download trendnot measured
      no download history for the selected registry
  • Tool quality≈73 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  88.0

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: widely adopted

  1.00

  Composite score

  88.0

• 2

  Atlassian Rovo MCP Server

  Community favourite

  atlassian/atlassian-mcp-server ↗

  Best for: Atlassian Cloud teams needing AI tools to access Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom through OAuth 2.1 or API token authentication.

  The Atlassian Rovo MCP Server provides an MCP interface that connects AI tools to Atlassian Cloud products including Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom. It requires Atlassian Cloud hosting and supports authentication through OAuth 2.1 or an API token.

  Score 81.9: show every number behind it

  • Adoption77 / 100 · weight 40%
    • GitHub stars77
    • npm downloadsnot measured
      no npm package
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance92 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence85
  • Momentum84 / 100 · weight 14%
    • Stars gained, relative to size91
    • Stars gained, absolute73
    • npm download trendnot measured
      no download history for the selected registry
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integrates100

  Weighted mean of the five

  81.9

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: widely adopted

  1.00

  Composite score

  81.9

• 3

  Atlassian Bitbucket MCP Server

  Abandoned but popular

  aashari/mcp-server-atlassian-bitbucket ↗

  Best for: AI-assisted Bitbucket Cloud repository and pull request work: it exposes tools to read, create, update, delete, and clone Bitbucket resources.

  It exposes six Bitbucket-focused tools (get, post, put, patch, delete, and clone) and documents MCP setup through npx for Claude Desktop and other AI assistants. It requires a Bitbucket Cloud account, not Bitbucket Server/Data Center, along with Node.js 18.0.0 or higher and Atlassian API token or app-password credentials.

  Score 69.3: show every number behind it

  • Adoption87 / 100 · weight 40%
    • GitHub stars55
    • npm downloads79
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance32 / 100 · weight 24%
    • Last commit touching this server42
    • Repository maintenance grade30
    • Commit cadence5
  • Momentum41 / 100 · weight 14%
    • Stars gained, relative to size25
    • Stars gained, absolute14
    • npm download trend100
  • Tool quality93 / 100 · weight 13%
    • Tool description quality85
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  69.3

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: widely adopted

  1.00

  Composite score

  69.3

• 4

  Atlassian Data Center MCP

  Steady

  b1ff/atlassian-dc-mcp ↗

  Best for: Jira Data Center deployments: it provides a product-specific MCP server package with an interactive setup that stores and validates credentials.

  The README documents separate MCP server packages for Jira, Confluence, and Bitbucket, each launched through npx and configured by an interactive setup subcommand that validates the host and API token. The project is community-maintained and not affiliated with, endorsed by, or supported by Atlassian.

  Score 58.4: show every number behind it

  • Adoption51 / 100 · weight 40%
    • GitHub stars51
    • npm downloadsnot measured
      no npm package
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance95 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence100
  • Momentum57 / 100 · weight 14%
    • Stars gained, relative to size70
    • Stars gained, absolute37
    • npm download trendnot measured
      no download history for the selected registry
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  68.7

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  58.4

• 5

  jira-easy-mcp

  Steady▲ 11

  IamSAL/jira-easy-mcp ↗

  Best for: Self-hosted Jira Server or Data Center environments that disallow API tokens: it authenticates with a plain username and password via HTTP Basic Authentication.

  jira-easy-mcp is an MCP server for self-hosted Jira Server/Data Center that uses HTTP Basic Authentication and documents tools for issues, projects, boards, sprints, JQL search, transitions, comments and worklogs. Before choosing it, note that it requires a self-hosted Jira Server/Data Center instance and JIRA_BASE_URL plus username/password credentials, with optional keychain storage depending on keytar.

  Score 53.1: show every number behind it

  • Adoption41 / 100 · weight 40%
    • GitHub stars17
    • npm downloads38
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance95 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence100
  • Momentum43 / 100 · weight 14%
    • Stars gained, relative to size36
    • Stars gained, absolute14
    • npm download trend91
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not 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

• 6

  Atlassian Jira MCP Server

  Abandoned but popular▼ 1

  aashari/mcp-server-atlassian-jira ↗

  Best for: Teams that need AI assistants to call arbitrary Jira REST endpoints: it provides generic HTTP-method tools for Jira API access.

  The README documents generic tools for GET, POST, PUT, PATCH, and DELETE requests to Jira REST endpoints, plus npx and npm installation and MCP configuration for AI assistants. It requires ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN to be configured before use.

  Score 52.9: show every number behind it

  • Adoption80 / 100 · weight 40%
    • GitHub stars47
    • npm downloads72
      downloads capped: not corroborated by repository audience
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance32 / 100 · weight 24%
    • Last commit touching this server42
    • Repository maintenance grade30
    • Commit cadence5
  • Momentum39 / 100 · weight 14%
    • Stars gained, relative to size29
    • Stars gained, absolute13
    • npm download trend86
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  62.2

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  52.9

• 7

  Atlassian Confluence MCP Server

  Abandoned but popular▼ 1

  aashari/mcp-server-atlassian-confluence ↗

  Best for: Confluence knowledge base access for AI assistants: it exposes five tools for GET, POST, PUT, PATCH, and DELETE Confluence API operations with JMESPath filtering.

  This server exposes five tools, conf_get, conf_post, conf_put, conf_patch, and conf_delete, which call Confluence API endpoints and support optional JMESPath filtering plus TOON or JSON output. Before choosing it, note that it requires ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, and ATLASSIAN_API_TOKEN credentials.

  Score 52.1: show every number behind it

  • Adoption77 / 100 · weight 40%
    • GitHub stars45
    • npm downloads70
      downloads capped: not corroborated by repository audience
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance32 / 100 · weight 24%
    • Last commit touching this server42
    • Repository maintenance grade30
    • Commit cadence5
  • Momentum16 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trend63
  • Tool quality91 / 100 · weight 13%
    • Tool description quality83
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  61.3

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  52.1

• 8

  Atlassian Bamboo MCP Server

  Steady▲ 1

  norus/atlassian-bamboo-mcp ↗

  Best for: Teams running Atlassian Bamboo CI/CD that need natural-language access to builds and deployments: it exposes 27 tools for build status, logs, plan management, queues, deployments.

  The server exposes 27 tools for Bamboo server health, projects, plans, branches, builds, build logs, build queues, deployment projects, deployment triggers, and deployment results. Before choosing it, note that it requires BAMBOO_URL and BAMBOO_TOKEN and that the README advises a patched Node.js release because it decompresses Brotli-encoded Bamboo responses.

  Score 52.0: show every number behind it

  • Adoption48 / 100 · weight 40%
    • GitHub stars21
    • npm downloads45
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance88 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence65
  • Momentum25 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • 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 measured
      not published by the vendor it integrates

  Weighted mean of the five

  61.2

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  52.0

• 9

  mcp-jira-scoped

  Steady▼ 1

  deepwired/mcp-jira ↗

  Best for: Teams moving to Atlassian scoped API tokens for Jira: it enforces granted scopes server-side before API calls, defaults to read-only, and offers a project allowlist.

  Its README documents MCP toolsets for Jira issues, search, comments, transitions, attachments, and sprints, backed by Atlassian scoped API tokens through api.atlassian.com with server-side scope enforcement. Before choosing it, note that it requires a scoped ATATT token rather than a classic token, needs JIRA_INSTANCE, JIRA_USER_EMAIL, and JIRA_API_TOKEN configured, and fails at startup on an unrecognised JIRA_SCOPES value.

  Score 48.3: show every number behind it

  • Adoption43 / 100 · weight 40%
    • GitHub stars17
    • npm downloads40
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance85 / 100 · weight 24%
    • Last commit touching this server88
    • Repository maintenance grade80
    • Commit cadence85
  • Momentum13 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trend51
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  56.8

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  48.3

• 10

  mcp-jira-stdio

  Steady

  freema/mcp-jira-stdio ↗

  Best for: Teams needing to create, update, comment on, and search Jira issues with JQL from Claude Desktop: it exposes 23 stdio tools covering those operations.

  mcp-jira-stdio exposes 23 tools for Jira issue and project operations, including JQL search, issue creation and updates, comments, transitions, attachments, and project metadata over stdio transport. Before choosing it, note that it requires Node.js v20 or higher and Jira connection details configured through the JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN environment variables.

  Score 47.2: show every number behind it

  • Adoption59 / 100 · weight 40%
    • GitHub stars29
    • npm downloads54
      downloads capped: not corroborated by repository audience
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance92 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence85
  • Momentum16 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trend66
  • Tool quality81 / 100 · weight 13%
    • Tool description quality73
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not 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: small audience

  0.70

  Composite score

  47.2

• 11

  atlassian-mcp-server

  Steady

  InfraMCP/atlassian-mcp-server ↗

  Best for: Teams running their own Atlassian OAuth 2.0 app: it handles browser-based PKCE authentication and lets Jira, Confluence and Service Desk modules be loaded selectively.

  Published on PyPI as atlassian-mcp-server, it splits Atlassian access into Jira, Confluence and Service Desk client modules covering issue search, creation, updates and comments, Confluence page reading and search, and service request handling, all behind an OAuth 2.0 flow with automatic token refresh. Before it can reach any data, an OAuth 2.0 integration must be created in the Atlassian Developer Console, pointed at the http://localhost:8080/callback URL, given the scopes the README lists, and installed on the target site.

  Score 44.4: show every number behind it

  • Adoption41 / 100 · weight 40%
    • GitHub stars17
    • PyPI downloads38
    • Used through Glamanot measured
      not 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
    • PyPI download trendnot measured
      no download history for the selected registry
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  52.2

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  44.4

• 12

  kanban-tui

  Community favourite▲ 1

  Zaloog/kanban-tui ↗

  Best for: Working with a kanban-tui board from an AI agent: it exposes task, board, and column management commands over MCP.

  It is an MCP server for kanban-tui, a terminal task manager, and its README documents CLI and MCP interfaces for AI agents to manage tasks, boards, and columns. Its MCP tool list has not been inspected, so verify its task, board, and column commands against the kanban-tui backend you intend to use, including Jira.

  Score 43.5: show every number behind it

  • Adoption68 / 100 · weight 40%
    • GitHub stars62
    • PyPI downloads40
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance88 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence65
  • Momentum49 / 100 · weight 14%
    • Stars gained, relative to size36
    • Stars gained, absolute26
    • PyPI download trend100
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  72.5

  × relevance: the keyword is tagged here

  0.60

  × continuity: actively changing

  1.00

  × evidence: widely adopted

  1.00

  Composite score

  43.5

• 13

  gadak

  Steady▼ 1

  midagedev/gadak ↗

  Best for: Answering aggregate questions JQL cannot express, such as open issues per epic: it mirrors Jira into local SQLite and exposes read-only SQL and full-text search.

  gadak mirrors selected Jira Cloud projects and Confluence spaces into one local SQLite file, and its MCP tools answer from that file with read-only SQL, full-text search across issues, comments and wiki pages, issue detail, and sprint and retro reads. Choosing it means running a sync first: the projects and spaces to mirror must be named, the wiki stays off until spaces are named, and reads reflect the last sync rather than live Jira.

  Score 43.3: show every number behind it

  • Adoption42 / 100 · weight 40%
    • GitHub stars42
    • npm downloadsnot measured
      no npm package
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance100 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade100
    • Commit cadence100
  • Momentum50 / 100 · weight 14%
    • Stars gained, relative to size63
    • Stars gained, absolute30
    • npm download trendnot measured
      no download history for the selected registry
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  65.3

  × relevance: the keyword is declared here

  0.78

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  43.3

• 14

  raalarcon-jira-mcp-server

  Dormant

  raalarcon9705/jira-mcp ↗

  Best for: Teams running Jira sprints and reading Confluence pages through an MCP client: it exposes sprint lifecycle, issue CRUD, comments, transitions, assignments, and a wiki query tool.

  The server connects an MCP client to Jira Cloud and exposes 24 tools for projects, issue types, issue CRUD, comments, transitions, assignments, users, agile boards, sprints, and Confluence pages by code. It requires JIRA_HOST, JIRA_EMAIL, and JIRA_API_TOKEN environment variables at setup.

  Score 42.5: show every number behind it

  • Adoption42 / 100 · weight 40%
    • GitHub stars21
    • npm downloads38
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance46 / 100 · weight 24%
    • Last commit touching this server68
    • Repository maintenance grade30
    • Commit cadence5
  • Momentum25 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trend100
  • Tool quality76 / 100 · weight 13%
    • Tool description quality68
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  50.0

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  42.5

• 15

  MCP Jira Server

  Abandoned but popular

  edrich13/mcp-jira-server ↗

  Best for: Self-hosted Jira environments using Personal Access Token authentication: it provides issue CRUD, JQL search, comments, project listing, assignments, and current-user lookup.

  The server interacts with a self-hosted Jira instance through Personal Access Token authentication and exposes tools for issue CRUD, JQL search, comments, project and issue-type lookup, assignments, and current-user details. Its setup requires a self-hosted Jira instance, a Personal Access Token, and the JIRA_BASE_URL and JIRA_PAT environment variables.

  Score 40.9: show every number behind it

  • Adoption60 / 100 · weight 40%
    • GitHub stars31
    • npm downloads56
      downloads capped: not corroborated by repository audience
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance38 / 100 · weight 24%
    • Last commit touching this server42
    • Repository maintenance grade55
    • Commit cadence5
  • Momentum45 / 100 · weight 14%
    • Stars gained, relative to size49
    • Stars gained, absolute21
    • npm download trend66
  • Tool quality76 / 100 · weight 13%
    • Tool description quality68
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  58.4

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: small audience

  0.70

  Composite score

  40.9

• 16

  mcp-atlassian

  Steady▲ 1

  SharkyND/mcp-atlassian ↗

  Best for: Agent workflows that need to read and write Jira beyond search: 73 tools cover issue creation, JQL search, sprints, worklogs and attachment summarization.

  For Jira it exposes 73 tools spanning JQL search, issue creation, updates and deletion, transitions, boards and sprints, worklogs, versions, issue links, and attachment download, summarization and image retrieval, with Confluence and Bitbucket covered by the same server. Before installing, note that it authenticates via an Atlassian API token, a Server/Data Center personal access token, or an OAuth 2.0 app, and that Xray for Jira is supported only on Server/Data Center deployments.

  Score 37.6: show every number behind it

  • Adoption36 / 100 · weight 40%
    • GitHub stars36
    • npm downloadsnot measured
      no npm package
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance92 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence85
  • Momentum0 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trendnot measured
      no download history for the selected registry
  • Tool quality63 / 100 · weight 13%
    • Tool description quality55
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  53.7

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: small audience

  0.70

  Composite score

  37.6

• 17

  Tempo MCP Server

  Dormant▲ 1

  ivelin-web/tempo-mcp-server ↗

  Best for: Teams needing browser and mobile access to Tempo worklog management: it can be hosted on Cloudflare Workers, with per-user MCP URLs.

  Tempo MCP Server exposes 7 tools for retrieving, creating, bulk creating, editing, and deleting Tempo worklogs, plus finding missing worklog days and aggregating worklog analytics by issue, account, day, week, or month. The remote option requires deploying to Cloudflare Workers with a KV namespace and an encryption key, and local stdio modes require Node.js 18+.

  Score 35.4: show every number behind it

  • Adoption53 / 100 · weight 40%
    • GitHub stars42
    • npm downloads46
    • Used through Glamanot measured
      not 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 size34
    • Stars gained, absolute15
    • 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 measured
      not published by the vendor it integrates

  Weighted mean of the five

  53.4

  × relevance: the keyword is declared here

  0.78

  × continuity: actively changing

  1.00

  × evidence: modest but real audience

  0.85

  Composite score

  35.4

• 18

  Atlassian Confluence MCP Server

  Steady▲ 1

  anuragagrawal0430/atlassian-confluence-mcp-server ↗

  Best for: Confluence Cloud, Server, or Data Center teams needing AI-assisted wiki reading and search: it exposes 28 tools, including CQL search and page body chunks.

  The server provides an MCP interface for Confluence Cloud, Server, and Data Center, exposing 28 tools for reading and searching spaces and pages, including CQL search, page body chunking, comments, attachments, labels, versions, watchers, permissions, tasks, and export URLs. It defaults to read-only mode, with mutating tools disabled unless CONFLUENCE_READ_ONLY is set to false.

  Score 33.5: show every number behind it

  • Adoption47 / 100 · weight 40%
    • GitHub stars19
    • npm downloads44
      downloads capped: not corroborated by repository audience
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance95 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence100
  • Momentum17 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trend67
  • Tool quality61 / 100 · weight 13%
    • Tool description quality53
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  60.9

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: no meaningful evidence of adoption

  0.55

  Composite score

  33.5

• 19

  jira-mcp

  Steady▼ 12

  softspark/jira-mcp ↗

  Best for: Teams managing multiple Jira Cloud instances: it documents multi-instance routing and Jira issue operations including search, comment, transition, log time, reassign, create, and delete.

  The @softspark/jira-mcp package is a Jira Cloud MCP server documented to sync and search issues, add comments, transition issues, log time, reassign, and create or delete issues. Installation uses the npm package @softspark/jira-mcp and registers the jira-mcp command; credentials and configuration live in ~/.softspark/jira-mcp/ and are shared with the separate Confluence server.

  Score 33.4: show every number behind it

  • Adoption42 / 100 · weight 40%
    • GitHub stars15
    • npm downloads40
      downloads capped: not corroborated by repository audience
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance95 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence100
  • Momentum25 / 100 · weight 14%
    • Stars gained, relative to size0
    • Stars gained, absolute0
    • npm download trend100
  • Tool quality≈65 / 100 · weight 13%
    • Tool description quality≈65
      tool descriptions not yet scored
    • Built and inspected by Glamanot measured
      never built and inspected by Glama
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  60.7

  × relevance: the keyword is dedicated here

  1.00

  × continuity: actively changing

  1.00

  × evidence: no meaningful evidence of adoption

  0.55

  Composite score

  33.4

• 20

  nable (finops-mcp)

  Steady

  getnable/finopsmcp ↗

  Best for: Before an agent applies an infrastructure change: it exposes estimate_change_cost to price the proposed change and check it against budget.

  nable is a local MCP server with 10 tools for connecting AWS, Azure, and GCP, summarizing spend by service, account, and region, preflighting proposed infrastructure costs, and checking AI and action policy gates. Before choosing it, note that Azure has no local credentials nable can safely auto-detect, so its connection flow requires a service-principal secret kept off the model.

  Score 32.4: show every number behind it

  • Adoption33 / 100 · weight 40%
    • GitHub stars33
    • npm downloadsnot measured
      no npm package
    • Used through Glamanot measured
      not used through Glama in the last 30 days
  • Maintenance95 / 100 · weight 24%
    • Last commit touching this server100
    • Repository maintenance grade80
    • Commit cadence100
  • Momentum27 / 100 · weight 14%
    • Stars gained, relative to size36
    • Stars gained, absolute15
    • npm download trendnot measured
      no download history for the selected registry
  • Tool quality81 / 100 · weight 13%
    • Tool description quality73
    • Built and inspected by Glama100
  • Trust100 / 100 · weight 9%
    • License100
    • Published by the vendor it integratesnot measured
      not published by the vendor it integrates

  Weighted mean of the five

  59.3

  × relevance: the keyword is declared here

  0.78

  × continuity: actively changing

  1.00

  × evidence: small audience

  0.70

  Composite score

  32.4

Questions people ask

Other comparisons

• Best Figma MCP servers
• Best Obsidian MCP servers
• Best YouTube MCP servers
• Best PostgreSQL MCP servers
• Best MySQL MCP servers
• Best GitHub MCP servers
• Best Slack MCP servers
• Best Notion MCP servers
• Best Linear MCP servers
• Best Discord MCP servers
• Best MongoDB MCP servers
• Best CRM MCP servers
• Best Payments MCP servers
• Best Ecommerce MCP servers
• Best Social Media MCP servers
• Best Browser Automation MCP servers
• Best CMS MCP servers
• Best Email MCP servers
• Best PDF MCP servers
• Best Kubernetes MCP servers
• Best Docker MCP servers
• Best AWS MCP servers
• Best Spreadsheets MCP servers
• Best SEO MCP servers
• Best Web Search MCP servers
• Best Web Scraping MCP servers
• Best Vector Database MCP servers
• Best Code Execution MCP servers
• Best Calendar MCP servers
• Best Observability MCP servers
• Best Image Generation MCP servers
• Best Speech & Transcription MCP servers
• Best Maps MCP servers
• Best Travel MCP servers
• Best Stock Market MCP servers
• Best Web Analytics MCP servers
• Best Memory MCP servers
• Best Documentation MCP servers
• Best Security MCP servers