Skip to main content
Glama

20 Best Jira MCP Servers, Compared (October 2026)

Updated 20 of 597 Jira servers in the Glama registryRebuilt weekly

The short answer

For Jira Cloud, install MCP Atlassian (sooperset/mcp-atlassian): it has 6,014 stars, gained 97 stars per 30 days, took a commit 29 days ago with 39 commits in the last 12 weeks, and documents JQL search plus jira_create_issue, jira_update_issue and jira_transition_issue. If your Jira is self-hosted and API tokens are not allowed, the better answer is jira-easy-mcp, which authenticates with a plain username and password and took a commit 4 days ago with 38 commits in the last 12 weeks. If you want Atlassian's own hosted bridge across Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom, use Atlassian Rovo MCP Server, which gained 54 stars per 30 days and took a commit 11 days ago. Do not pick on download volume alone: Atlassian Jira MCP Server has 15,369 npm downloads in a typical week but 0 commits in the last 12 weeks and a last commit 226 days ago.

Whichever you choose, give it the narrowest access that still works (a read-only credential, a replica, a scratch account), and widen it only once you have watched what your agent actually asks for.

Glama operates the MCP registry these numbers are measured from, and sells MCP hosting and a gateway. No position on this page is paid for. How the registry is built.

Quick picks

  • 1MCP Atlassian : Jira Cloud issue search and updates from an MCP client: the README documents JQL search plus jira_create_issue, jira_update_issue, and jira_transition_issue.
  • 2Atlassian Rovo MCP Server : Organizations on Atlassian Cloud needing MCP access to Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom: it is the official cloud-hosted bridge.
  • 3Atlassian Bitbucket MCP Server : Bitbucket Cloud teams wanting AI access to repositories, pull requests, and code: it exposes read, write, and clone tools for those resources.
  • 4Atlassian Data Center MCP : Jira Data Center teams: the setup CLI validates host and token before storing credentials in the Keychain or a 0600 env file.
  • 5Atlassian Confluence MCP Server : AI assistants needing read and write access to Confluence: it exposes five generic tools for get, post, put, patch, and delete API operations.

Which one, for your situation

Your situationWhat to use
Jira Cloud issue work from an MCP clientMCP Atlassian, because it documents JQL search plus jira_create_issue, jira_update_issue and jira_transition_issue for Atlassian Cloud, and took a commit 29 days ago.
Self-hosted Jira where API tokens are disallowedjira-easy-mcp, because it uses HTTP Basic Authentication with a plain username and password, and took a commit 4 days ago with 38 commits in the last 12 weeks.
Must use Atlassian's official hosted bridgeAtlassian Rovo MCP Server, the official cloud-hosted bridge for Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom, with a commit 11 days ago.
Want offline SQL and full-text search over Jiragadak, which mirrors selected projects and spaces into local SQLite and answers MCP reads from that file, with a commit 0 days ago.
On Atlassian scoped tokens, writes kept restrictedmcp-jira-scoped, which authenticates against api.atlassian.com, enforces granted scopes server-side and defaults to read-only.

Top MCP servers for Jira

Best forProfile
1
sooperset/mcp-atlassian
Jira Cloud issue search and updates from an MCP client: the README documents JQL search plus jira_create_issue, jira_update_issue, and jira_transition_issue.Community favourite6,014+9729 days ago89.1
2
atlassian/atlassian-mcp-server
Organizations on Atlassian Cloud needing MCP access to Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom: it is the official cloud-hosted bridge.Community favourite1,105+5411 days ago81.1
3
aashari/mcp-server-atlassian-bitbucket
Bitbucket Cloud teams wanting AI access to repositories, pull requests, and code: it exposes read, write, and clone tools for those resources.Abandoned but popular163+1226 days ago68.8
4
b1ff/atlassian-dc-mcp
Jira Data Center teams: the setup CLI validates host and token before storing credentials in the Keychain or a 0600 env file.Steady103+46 days ago57.5
5
aashari/mcp-server-atlassian-confluence
AI assistants needing read and write access to Confluence: it exposes five generic tools for get, post, put, patch, and delete API operations.Abandoned but popular62+1320 days ago56.1
6
aashari/mcp-server-atlassian-jira
Developers needing raw Jira REST access from an AI assistant: it exposes GET, POST, PUT, PATCH and DELETE tools that take an API path.Abandoned but popular770226 days ago52.3
7
softspark/jira-mcp
Multi-instance Jira Cloud setups: it documents per-project configuration and multi-instance routing while keeping Jira and Confluence tool lists separate.Steady3024 days ago50.8
8
norus/atlassian-bamboo-mcp
Teams needing natural-language Bamboo CI/CD operations: the server exposes 27 tools for build status, logs, triggering builds, and deployment management.Steady6+141 days ago50.4
9
deepwired/mcp-jira
Teams using Atlassian scoped API tokens: it authenticates against api.atlassian.com, enforces granted scopes server-side, and defaults to read-only.Steady4028 days ago49.4
10
freema/mcp-jira-stdio
Claude Desktop or Claude Code users managing Jira issues: it exposes 23 stdio tools for JQL search, issue creation, updates, comments, transitions, and attachments.Steady14016 days ago46.4
11
raalarcon9705/jira-mcp
Managing Jira issues and agile sprints through an MCP client: it exposes issue CRUD, comment, transition, assignment, user, board and sprint tools.Dormant6+1142 days ago42.4
12
midagedev/gadak
Teams needing offline SQL and full-text search over Jira and Confluence: it mirrors selected projects and spaces into local SQLite for MCP reads.Steady43+3today41.8
13
InfraMCP/atlassian-mcp-server
When an AI agent must create or update Jira issues and read Confluence pages with OAuth 2.0: the README documents those Jira and Confluence operations.Dormant40211 days ago40.9
14
Zaloog/kanban-tui
When kanban-tui is configured with its Jira backend: it exposes task, board, and column management commands for AI agents.Community favourite286+351 days ago40.2
15
IamSAL/jira-easy-mcp
Self-hosted Jira Server or Data Center where API tokens are disallowed: it uses HTTP Basic Authentication with a plain username and password.Steady3No snapshot history4 days ago39.2
16
SharkyND/mcp-atlassian
Jira teams working from an MCP client that need issue creation, transitions, sprints, worklogs, attachments, and version management: it exposes 73 tools.Steady2709 days ago39.0
17
yogeshhrathod/JiraMCP
Self-hosted Jira Server or Data Center teams needing PAT-authenticated issue management, JQL search, comments, transitions, and custom fields: it exposes 27 tools.Steady1018 days ago37.8
18
edrich13/mcp-jira-server
Self-hosted Jira with Personal Access Token authentication: it exposes issue CRUD, JQL search, comments, assignments, and project tools.Abandoned but popular14+1264 days ago37.0
19
ivelin-web/tempo-mcp-server
Teams logging Tempo worklogs in Jira: it exposes seven tools covering retrieve, create, bulk create, edit, delete, missing-day reports, and analytics.Dormant47+3107 days ago36.5
20
namcpgem/gem-jira-mcp
Teams running Jira Server/Data Center that need an AI assistant to read and write tickets, comments, worklogs, sprints, and links via direct REST API v2.Steady2+112 days ago33.4

The ranking, with the evidence

Each position is a weighted mean of adoption (40%), maintenance (24%), momentum (14%), tool description quality (13%) and trust (9%), multiplied by three attenuators: how directly the server is about Jira (named for it, declaring it, tagged with it, or merely mentioning it), whether its repository is still moving, and how much independent evidence of adoption it has. Open the score on any entry to see every number, including the ones marked ≈, which were imputed from the median of the other candidates rather than measured. The maintenance grade on each entry is mostly issue responsiveness, release recency and open security alerts rather than commits, so a recent commit beside a low grade is two different measurements rather than a contradiction.

  • Abandoned but popular: People use it, but its default branch has stopped moving. Fine to keep running, risky to adopt.
  • Community favourite: Widely adopted and still actively maintained.
  • Dormant: Neither changing nor widely adopted. Here because it still matches the search.
  • Emerging: Small audience, growing quickly, maintained. The bet with the most upside.
  • Steady: Maintained, modest audience, no surprises in either direction.
  • 1

    MCP Atlassian

    Community favouriteNo change
    sooperset/mcp-atlassian ↗

    Best for: Jira Cloud issue search and updates from an MCP client: the README documents JQL search plus jira_create_issue, jira_update_issue, and jira_transition_issue.

    MCP Atlassian is a Model Context Protocol server for Atlassian products that documents Jira and Confluence tools for JQL and CQL search, issue and page retrieval, creation, updates, transitions, and comments. The main consideration before choosing it is deployment support: its description states it is designed specifically for Atlassian Cloud and does not support Server or Data Center, while the README also includes authentication guidance for Server and Data Center.

    GitHub stars
    6,014
    Stars over the last 90 days: 5,610 at the earliest of 86 readings and 6,019 at the latest, up 409.
    Stars / 30 days
    +97
    npm / typical week
    Ships no npm package
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    29 days ago
    Commits / 12 weeks
    39
    Weekly commits over the last 12 weeks, oldest first: 7, 2, 8, 9, 5, 4, 2, 2, 0, 0, 0, 0. 39 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 89.1: show every number behind it
    • Adoption94 / 100 · weight 40%
      • GitHub stars94
      • 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
    • Momentum63 / 100 · weight 14%
      • Stars gained, relative to size52
      • Stars gained, absolute80
      • 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
    89.1
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: widely adopted
    1.00
    Composite score
    89.1
  • 2

    Atlassian Rovo MCP Server

    Community favourite▲ 1
    atlassian/atlassian-mcp-server ↗

    Best for: Organizations on Atlassian Cloud needing MCP access to Jira, Confluence, Jira Service Management, Bitbucket, Compass, and Loom: it is the official cloud-hosted bridge.

    Atlassian Rovo MCP Server is an MCP-compatible server hosted on Atlassian Cloud that connects AI tools to Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and the wider Atlassian platform. Before choosing it, note that it assumes an Atlassian Cloud environment and OAuth 2.1 or API token authentication.

    GitHub stars
    1,105
    Stars over the last 90 days: 920 at the earliest of 16 readings and 1,105 at the latest, up 185.
    Stars / 30 days
    +54
    npm / typical week
    Ships no npm package
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    11 days ago
    Commits / 12 weeks
    26
    Weekly commits over the last 12 weeks, oldest first: 2, 0, 1, 3, 3, 9, 4, 2, 0, 0, 2, 0. 26 in total, and the last figure is the current week so far.
    Maintenance grade
    B
    Tool descriptions
    Not graded
    Score 81.1: show every number behind it
    • Adoption76 / 100 · weight 40%
      • GitHub stars76
      • 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
    • Momentum80 / 100 · weight 14%
      • Stars gained, relative to size86
      • Stars gained, absolute70
      • 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.1
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: widely adopted
    1.00
    Composite score
    81.1
  • 3

    Atlassian Bitbucket MCP Server

    Abandoned but popular▼ 1
    aashari/mcp-server-atlassian-bitbucket ↗

    Best for: Bitbucket Cloud teams wanting AI access to repositories, pull requests, and code: it exposes read, write, and clone tools for those resources.

    The server exposes six tools (bb_get, bb_post, bb_put, bb_patch, bb_delete, and bb_clone) that let an MCP client read, create, replace, partially update, and delete Bitbucket resources such as repositories and pull requests, or clone a repository to a local path. It assumes Node.js 18.0.0 or higher, a Bitbucket Cloud account rather than Bitbucket Server or Data Center, and either a scoped API token or a legacy app password for authentication.

    GitHub stars
    163
    Stars over the last 90 days: 160 at the earliest of 11 readings and 163 at the latest, up 3.
    Stars / 30 days
    +1
    npm / typical week
    4K
    PyPI / typical week
    no attributed package
    Tools exposed
    6
    Last commit
    226 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    D
    Tool descriptions
    A
    Score 68.8: show every number behind it
    • Adoption85 / 100 · weight 40%
      • GitHub stars55
      • npm downloads77
      • 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
    • Momentum19 / 100 · weight 14%
      • Stars gained, relative to size27
      • Stars gained, absolute15
      • npm download trend11
    • 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
    68.8
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: widely adopted
    1.00
    Composite score
    68.8
  • 4

    Atlassian Data Center MCP

    SteadyNo change
    b1ff/atlassian-dc-mcp ↗

    Best for: Jira Data Center teams: the setup CLI validates host and token before storing credentials in the Keychain or a 0600 env file.

    The README documents three MCP servers for Atlassian Data Center (Jira, Confluence, and Bitbucket), each configured through an interactive setup subcommand that validates the host, API base path, and token against the target product before saving them, after which the servers boot with no environment variables set. It targets Atlassian Data Center deployments, and the README states the project is community-maintained and not affiliated with, endorsed by, or supported by Atlassian.

    GitHub stars
    103
    Stars over the last 90 days: 83 at the earliest of 13 readings and 103 at the latest, up 20.
    Stars / 30 days
    +4
    npm / typical week
    Ships no npm package
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    6 days ago
    Commits / 12 weeks
    59
    Weekly commits over the last 12 weeks, oldest first: 4, 1, 0, 3, 10, 18, 2, 3, 5, 0, 1, 12. 59 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 57.5: show every number behind it
    • Adoption50 / 100 · weight 40%
      • GitHub stars50
      • 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
    • Momentum43 / 100 · weight 14%
      • Stars gained, relative to size52
      • Stars gained, absolute29
      • 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
    67.6
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    57.5
  • 5

    Atlassian Confluence MCP Server

    Abandoned but popularNo change
    aashari/mcp-server-atlassian-confluence ↗

    Best for: AI assistants needing read and write access to Confluence: it exposes five generic tools for get, post, put, patch, and delete API operations.

    The Atlassian Confluence MCP Server exposes five tools named conf_get, conf_post, conf_put, conf_patch, and conf_delete, which call arbitrary Confluence API paths and support optional query parameters, jq filtering, and TOON or JSON output. Choosing it assumes Atlassian credentials (site name, user email, and API token) are configured through environment variables, a .env file, or a ~/.mcp/configs.json file.

    GitHub stars
    62
    Stars over the last 90 days: 60 at the earliest of 10 readings and 62 at the latest, up 2.
    Stars / 30 days
    +1
    npm / typical week
    7K
    PyPI / typical week
    no attributed package
    Tools exposed
    5
    Last commit
    320 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    C
    Tool descriptions
    A
    Score 56.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
    • Maintenance38 / 100 · weight 24%
      • Last commit touching this server42
        dated from the last commit on the default branch, re-read from GitHub at publication; github.com shows a push 238 days ago, which counts every ref; the stored date would have published 238 days ago
      • Repository maintenance grade55
      • Commit cadence5
    • Momentum39 / 100 · weight 14%
      • Stars gained, relative to size34
      • Stars gained, absolute16
      • npm download trend76
    • 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
    66.0
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    56.1
  • 6

    Atlassian Jira MCP Server

    Abandoned but popularNo change
    aashari/mcp-server-atlassian-jira ↗

    Best for: Developers needing raw Jira REST access from an AI assistant: it exposes GET, POST, PUT, PATCH and DELETE tools that take an API path.

    The server is an npm package that runs over STDIO and exposes generic GET, POST, PUT, PATCH and DELETE tools taking a Jira REST API path, with optional JMESPath filtering and TOON output by default. Choosing it means supplying an Atlassian API token, account email and site name as credentials, and composing correct endpoint paths yourself, since the tools wrap any Jira API route rather than modeled issue operations.

    GitHub stars
    77
    Stars over the last 90 days: 72 at the earliest of 10 readings and 77 at the latest, up 5.
    Stars / 30 days
    0
    npm / typical week
    15.4K
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    226 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    D
    Tool descriptions
    Not graded
    Score 52.3: show every number behind it
    • Adoption79 / 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
    • Maintenance46 / 100 · weight 24%
      • Last commit touching this server68
      • Repository maintenance grade30
      • Commit cadence5
    • Momentum9 / 100 · weight 14%
      • Stars gained, relative to size0
      • Stars gained, absolute0
      • npm download trend36
    • Tool quality≈65 / 100 · weight 13%
      • Tool description quality≈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
    61.5
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    52.3
  • 7

    jira-mcp

    SteadyNo change
    softspark/jira-mcp ↗

    Best for: Multi-instance Jira Cloud setups: it documents per-project configuration and multi-instance routing while keeping Jira and Confluence tool lists separate.

    The @softspark/jira-mcp package is documented as a Jira MCP server for Atlassian Cloud with operations for sync, search, comments, transitions, time logging, reassignment, issue creation, and deletion, and it shares configuration and an API token with a separate Confluence server in the same repository. Its scope is Jira only: Confluence pages, blog posts, comments, labels, attachments, restrictions, and whiteboards are handled by the separate @softspark/confluence-mcp package.

    GitHub stars
    3
    Stars over the last 90 days: 1 at the earliest of 14 readings and 3 at the latest, up 2.
    Stars / 30 days
    0
    npm / typical week
    70
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    24 days ago
    Commits / 12 weeks
    60
    Weekly commits over the last 12 weeks, oldest first: 3, 4, 0, 1, 0, 10, 28, 5, 9, 0, 0, 0. 60 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 50.8: show every number behind it
    • Adoption42 / 100 · weight 40%
      • GitHub stars15
      • npm downloads39
      • 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
    • Momentum12 / 100 · weight 14%
      • Stars gained, relative to size0
      • Stars gained, absolute0
      • npm download trend48
    • 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
    59.8
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    50.8
  • 8

    Atlassian Bamboo MCP Server

    SteadyNo change
    norus/atlassian-bamboo-mcp ↗

    Best for: Teams needing natural-language Bamboo CI/CD operations: the server exposes 27 tools for build status, logs, triggering builds, and deployment management.

    Atlassian Bamboo MCP Server connects AI assistants to Bamboo CI/CD and exposes 27 tools for server health, projects, plans, branches, builds, queues, logs, and deployments. Before choosing it, note that it requires Node.js 18+ and a Bamboo personal access token supplied through BAMBOO_URL and BAMBOO_TOKEN; BAMBOO_PROXY is optional for corporate environments.

    GitHub stars
    6
    Stars over the last 90 days: 4 at the earliest of 10 readings and 6 at the latest, up 2.
    Stars / 30 days
    +1
    npm / typical week
    112
    PyPI / typical week
    no attributed package
    Tools exposed
    27
    Last commit
    41 days ago
    Commits / 12 weeks
    2
    Weekly commits over the last 12 weeks, oldest first: 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0. 2 in total, and the last figure is the current week so far.
    Maintenance grade
    B
    Tool descriptions
    B
    Score 50.4: show every number behind it
    • Adoption47 / 100 · weight 40%
      • GitHub stars21
      • npm downloads44
      • Used through Glamanot measured
        not used through Glama in the last 30 days
    • Maintenance83 / 100 · weight 24%
      • Last commit touching this server100
      • Repository maintenance grade80
      • Commit cadence40
    • Momentum22 / 100 · weight 14%
      • Stars gained, relative to size39
      • Stars gained, absolute16
      • npm download trend0
    • Tool quality66 / 100 · weight 13%
      • Tool description quality57
      • Built and inspected by Glama100
    • Trust100 / 100 · weight 9%
      • License100
      • Published by the vendor it integratesnot measured
        not published by the vendor it integrates
    Weighted mean of the five
    59.3
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    50.4
  • 9

    mcp-jira-scoped

    SteadyNo change
    deepwired/mcp-jira ↗

    Best for: Teams using Atlassian scoped API tokens: it authenticates against api.atlassian.com, enforces granted scopes server-side, and defaults to read-only.

    It exposes Jira tools for issues, search, comments, transitions, attachments, and boards or sprints, registered in toolsets selected at startup, with destructive operations requiring an explicit confirm flag. The thing to know before adopting it is that it authenticates only with scoped tokens minted through Atlassian's scope picker against api.atlassian.com, and because Atlassian cannot return or edit a token's scopes after creation, changing them means minting a new token.

    GitHub stars
    4
    Stars over the last 90 days: 3 at the earliest of 10 readings and 4 at the latest, up 1.
    Stars / 30 days
    0
    npm / typical week
    77
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    28 days ago
    Commits / 12 weeks
    19
    Weekly commits over the last 12 weeks, oldest first: 0, 0, 0, 0, 0, 0, 0, 0, 19, 0, 0, 0. 19 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 49.4: 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
    • Maintenance97 / 100 · weight 24%
      • Last commit touching this server100
      • Repository maintenance grade100
      • Commit cadence85
    • Momentum2 / 100 · weight 14%
      • Stars gained, relative to size0
      • Stars gained, absolute0
      • npm download trend7
    • 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
    58.1
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    49.4
  • 10

    mcp-jira-stdio

    SteadyNo change
    freema/mcp-jira-stdio ↗

    Best for: Claude Desktop or Claude Code users managing Jira issues: it exposes 23 stdio tools for JQL search, issue creation, updates, comments, transitions, and attachments.

    mcp-jira-stdio is a stdio MCP server that exposes 23 Jira tools for reading, creating, updating, searching, commenting on, transitioning, linking, and attaching to issues and projects. Before choosing it, note that it requires Node.js 20 or higher and Jira credentials supplied through environment variables such as JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN.

    GitHub stars
    14
    Stars over the last 90 days: 14 at the earliest of 11 readings and 14 at the latest, unchanged.
    Stars / 30 days
    0
    npm / typical week
    784
    PyPI / typical week
    no attributed package
    Tools exposed
    23
    Last commit
    16 days ago
    Commits / 12 weeks
    20
    Weekly commits over the last 12 weeks, oldest first: 1, 0, 8, 0, 0, 5, 0, 4, 0, 2, 0, 0. 20 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    A
    Score 46.4: 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
    • Maintenance97 / 100 · weight 24%
      • Last commit touching this server100
      • Repository maintenance grade100
      • Commit cadence85
    • Momentum0 / 100 · weight 14%
      • Stars gained, relative to size0
      • Stars gained, absolute0
      • npm download trend0
    • Tool 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
    66.3
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: small audience
    0.70
    Composite score
    46.4
  • 11

    raalarcon-jira-mcp-server

    DormantNo change
    raalarcon9705/jira-mcp ↗

    Best for: Managing Jira issues and agile sprints through an MCP client: it exposes issue CRUD, comment, transition, assignment, user, board and sprint tools.

    The raalarcon-jira-mcp-server exposes 24 tools for Jira projects, issue types, issue CRUD, comments, transitions, assignments, users, agile boards, sprints, and Confluence page content retrieval. Before choosing it, know that it assumes a Jira Cloud instance configured with JIRA_HOST, JIRA_EMAIL, and JIRA_API_TOKEN, and its Confluence support is limited to querying page content by code.

    GitHub stars
    6
    Stars over the last 90 days: 5 at the earliest of 11 readings and 6 at the latest, up 1.
    Stars / 30 days
    +1
    npm / typical week
    70
    PyPI / typical week
    no attributed package
    Tools exposed
    24
    Last commit
    142 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    D
    Tool descriptions
    A
    Score 42.4: show every number behind it
    • Adoption43 / 100 · weight 40%
      • GitHub stars21
      • npm downloads39
      • 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
    • Momentum22 / 100 · weight 14%
      • Stars gained, relative to size38
      • Stars gained, absolute15
      • npm download trend0
    • Tool quality76 / 100 · weight 13%
      • Tool description quality68
      • Built and inspected by Glama100
    • Trust100 / 100 · weight 9%
      • License100
      • Published by the vendor it integratesnot measured
        not published by the vendor it integrates
    Weighted mean of the five
    49.9
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    42.4
  • 12

    gadak

    SteadyNo change
    midagedev/gadak ↗

    Best for: Teams needing offline SQL and full-text search over Jira and Confluence: it mirrors selected projects and spaces into local SQLite for MCP reads.

    gadak mirrors selected Jira Cloud or Jira Server projects (or Linear, or its built-in tracker) and Confluence spaces into a local SQLite file, then exposes MCP tools for read-only SQL, full-text search across issues, comments and wiki pages, issue detail, and sprint and retro reads. Its constraint is a local SQLite mirror populated first: Jira Cloud connections use an API token created with no scopes, and Confluence Server is not covered.

    GitHub stars
    43
    Stars over the last 90 days: 39 at the earliest of 9 readings and 43 at the latest, up 4.
    Stars / 30 days
    +3
    npm / typical week
    Ships no npm package
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    today
    Commits / 12 weeks
    2,235
    Weekly commits over the last 12 weeks, oldest first: 0, 0, 309, 231, 529, 365, 256, 363, 159, 10, 13, 0. 2,235 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 41.8: show every number behind it
    • Adoption41 / 100 · weight 40%
      • GitHub stars41
      • 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
    • Momentum37 / 100 · weight 14%
      • Stars gained, relative to size47
      • Stars gained, absolute22
      • 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
    63.0
    × relevance: the keyword is declared here
    0.78
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    41.8
  • 13

    atlassian-mcp-server

    DormantNew
    InfraMCP/atlassian-mcp-server ↗

    Best for: When an AI agent must create or update Jira issues and read Confluence pages with OAuth 2.0: the README documents those Jira and Confluence operations.

    The README documents a Python MCP server that authenticates to Atlassian Cloud through OAuth 2.0 with PKCE and provides separate Jira, Confluence, and Service Desk clients for issue, page, and service request operations. Before it can be used, an Atlassian OAuth 2.0 integration must be created, configured with the listed scopes, installed to the target site, and supplied with client credentials through environment variables.

    GitHub stars
    4
    Stars over the last 90 days: 4 at the earliest of 11 readings and 4 at the latest, unchanged.
    Stars / 30 days
    0
    npm / typical week
    Ships no npm package
    PyPI / typical week
    66
    atlassian-mcp-server
    Tools exposed
    never inspected
    Last commit
    211 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    B
    Tool descriptions
    Not graded
    Score 40.9: show every number behind it
    • Adoption41 / 100 · weight 40%
      • GitHub stars17
      • PyPI downloads39
      • Used through Glamanot measured
        not used through Glama in the last 30 days
    • Maintenance58 / 100 · weight 24%
      • Last commit touching this server68
        dated from the last commit on the default branch, re-read from GitHub at publication; github.com shows a push 94 days ago, which counts every ref; the stored date would have published 94 days ago
      • Repository maintenance grade80
      • Commit cadence5
    • 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
    48.1
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    40.9
  • 14

    kanban-tui

    Community favourite▼ 1
    Zaloog/kanban-tui ↗

    Best for: When kanban-tui is configured with its Jira backend: it exposes task, board, and column management commands for AI agents.

    The kanban-tui MCP server exposes task, board, and column management commands so AI agents can interact with the terminal task manager, and its README documents a CLI interface and an MCP Server section for co-op mode. It is not a direct Jira connector: it requires kanban-tui and relies on its Jira backend, which connects via API key, queries tasks via JQL, and defines columns by task transitions.

    GitHub stars
    286
    Stars over the last 90 days: 267 at the earliest of 10 readings and 286 at the latest, up 19.
    Stars / 30 days
    +3
    npm / typical week
    Ships no npm package
    PyPI / typical week
    63
    kanban-tui
    Tools exposed
    never inspected
    Last commit
    51 days ago
    Commits / 12 weeks
    6
    Weekly commits over the last 12 weeks, oldest first: 0, 0, 1, 0, 5, 0, 0, 0, 0, 0, 0, 0. 6 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 40.2: show every number behind it
    • Adoption64 / 100 · weight 40%
      • GitHub stars61
      • PyPI downloads19
        PyPI downloads show no weekday rhythm; halved
      • Used through Glamanot measured
        not used through Glama in the last 30 days
    • Maintenance86 / 100 · weight 24%
      • Last commit touching this server88
      • Repository maintenance grade100
      • Commit cadence65
    • Momentum22 / 100 · weight 14%
      • Stars gained, relative to size33
      • Stars gained, absolute24
      • PyPI download trend0
    • 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
    67.0
    × relevance: the keyword is tagged here
    0.60
    × continuity: actively changing
    1.00
    × evidence: widely adopted
    1.00
    Composite score
    40.2
  • 15

    jira-easy-mcp

    Steady▼ 1
    IamSAL/jira-easy-mcp ↗

    Best for: Self-hosted Jira Server or Data Center where API tokens are disallowed: it uses HTTP Basic Authentication with a plain username and password.

    The README documents a stdio MCP server, installed via npx or claude mcp add, that exposes tools for JQL search, issue retrieval and creation, issue updates, comments, transitions, worklogs, sprints, links, filter URL generation, and attachment uploads. It assumes a self-hosted Jira Server or Data Center instance and credentials supplied through JIRA_BASE_URL, JIRA_USERNAME, and JIRA_PASSWORD, or stored in an OS keychain under the service name JiraMCP.

    GitHub stars
    3
    Stars / 30 days
    no snapshot history
    npm / typical week
    39
    PyPI / typical week
    no attributed package
    Tools exposed
    never inspected
    Last commit
    4 days ago
    Commits / 12 weeks
    38
    Weekly commits over the last 12 weeks, oldest first: 0, 0, 0, 0, 0, 1, 0, 0, 0, 6, 0, 31. 38 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    Not graded
    Score 39.2: show every number behind it
    • Adoption36 / 100 · weight 40%
      • GitHub stars15
      • npm downloads34
      • 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
    • Momentum0 / 100 · weight 14%
      • Stars gained, relative to sizenot measured
        no snapshot history yet
      • Stars gained, absolutenot measured
        no snapshot history yet
      • npm download trend0
    • 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.0
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: small audience
    0.70
    Composite score
    39.2
  • 16

    mcp-atlassian

    Steady▼ 1
    SharkyND/mcp-atlassian ↗

    Best for: Jira teams working from an MCP client that need issue creation, transitions, sprints, worklogs, attachments, and version management: it exposes 73 tools.

    It is an MCP server for Atlassian products (Confluence, Jira, Bitbucket, and Xray for Jira) that exposes 73 tools for searching, creating, and updating issues, pages, and test results. A constraint to note: Xray for Jira is supported only on Server/Data Center deployments and always uses the Jira URL and credentials configured for Jira.

    GitHub stars
    27
    Stars over the last 90 days: 28 at the earliest of 14 readings and 27 at the latest, down 1.
    Stars / 30 days
    0
    npm / typical week
    Ships no npm package
    PyPI / typical week
    no attributed package
    Tools exposed
    73
    Last commit
    9 days ago
    Commits / 12 weeks
    36
    Weekly commits over the last 12 weeks, oldest first: 2, 9, 1, 1, 1, 0, 2, 5, 1, 1, 10, 3. 36 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    B
    Score 39.0: 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
    • Maintenance100 / 100 · weight 24%
      • Last commit touching this server100
      • Repository maintenance grade100
      • Commit cadence100
    • 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
    55.7
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: small audience
    0.70
    Composite score
    39.0
  • 17

    Jira MCP Server

    Steady▼ 1
    yogeshhrathod/JiraMCP ↗

    Best for: Self-hosted Jira Server or Data Center teams needing PAT-authenticated issue management, JQL search, comments, transitions, and custom fields: it exposes 27 tools.

    Jira MCP Server connects to a self-hosted Jira instance with Personal Access Token authentication and exposes 27 tools covering issue retrieval, creation, updates, deletion, assignment, JQL searches, comments, transitions, projects, users, links, watchers, fields, and metadata. Before choosing it, note that it requires a self-hosted Jira Server or Data Center instance and a Personal Access Token.

    GitHub stars
    1
    Stars over the last 90 days: 1 at the earliest of 10 readings and 1 at the latest, unchanged.
    Stars / 30 days
    0
    npm / typical week
    28
    PyPI / typical week
    no attributed package
    Tools exposed
    27
    Last commit
    18 days ago
    Commits / 12 weeks
    6
    Weekly commits over the last 12 weeks, oldest first: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 0. 6 in total, and the last figure is the current week so far.
    Maintenance grade
    B
    Tool descriptions
    B
    Score 37.8: show every number behind it
    • Adoption32 / 100 · weight 40%
      • GitHub stars8
      • npm downloads31
      • 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
    • Momentum15 / 100 · weight 14%
      • Stars gained, relative to size0
      • Stars gained, absolute0
      • npm download trend60
    • Tool quality68 / 100 · weight 13%
      • Tool description quality60
      • 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
    54.0
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: small audience
    0.70
    Composite score
    37.8
  • 18

    MCP Jira Server

    Abandoned but popular▼ 1
    edrich13/mcp-jira-server ↗

    Best for: Self-hosted Jira with Personal Access Token authentication: it exposes issue CRUD, JQL search, comments, assignments, and project tools.

    MCP Jira Server interacts with a self-hosted Jira instance through the Jira REST API and exposes 12 tools for issue retrieval, creation, update, deletion, JQL search, comments, assignments, projects, issue types, and current-user lookup. Before choosing it, note that it assumes a self-hosted Jira instance and a Personal Access Token supplied through JIRA_BASE_URL and JIRA_PAT.

    GitHub stars
    14
    Stars over the last 90 days: 9 at the earliest of 11 readings and 15 at the latest, up 6.
    Stars / 30 days
    +1
    npm / typical week
    504
    PyPI / typical week
    no attributed package
    Tools exposed
    12
    Last commit
    264 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    D
    Tool descriptions
    A
    Score 37.0: 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
    • Maintenance32 / 100 · weight 24%
      • Last commit touching this server42
      • Repository maintenance grade30
      • Commit cadence5
    • Momentum21 / 100 · weight 14%
      • Stars gained, relative to size37
      • Stars gained, absolute15
      • npm download trend0
    • Tool quality76 / 100 · weight 13%
      • Tool description quality68
      • Built and inspected by Glama100
    • Trust100 / 100 · weight 9%
      • License100
      • Published by the vendor it integratesnot measured
        not published by the vendor it integrates
    Weighted mean of the five
    52.9
    × relevance: the keyword is dedicated here
    1.00
    × continuity: actively changing
    1.00
    × evidence: small audience
    0.70
    Composite score
    37.0
  • 19

    Tempo MCP Server

    Dormant▼ 1
    ivelin-web/tempo-mcp-server ↗

    Best for: Teams logging Tempo worklogs in Jira: it exposes seven tools covering retrieve, create, bulk create, edit, delete, missing-day reports, and analytics.

    Tempo MCP Server wraps Tempo's worklog API in seven MCP tools for retrieving, creating, bulk creating, editing and deleting worklogs, plus a missing-worklog-days report and worklog analytics grouped by issue, account, day, week or month. Choosing it means supplying a Jira Cloud instance with a Tempo API token and a Jira API token (OAuth 2.0 PKCE avoids the latter), and Node.js 18+ is required only for the local stdio modes.

    GitHub stars
    47
    Stars over the last 90 days: 42 at the earliest of 10 readings and 47 at the latest, up 5.
    Stars / 30 days
    +3
    npm / typical week
    133
    PyPI / typical week
    no attributed package
    Tools exposed
    7
    Last commit
    107 days ago
    Commits / 12 weeks
    0
    Maintenance grade
    B
    Tool descriptions
    C
    Score 36.5: show every number behind it
    • Adoption52 / 100 · weight 40%
      • GitHub stars42
      • npm downloads45
      • Used through Glamanot measured
        not used through Glama in the last 30 days
    • Maintenance69 / 100 · weight 24%
      • Last commit touching this server88
      • Repository maintenance grade80
      • Commit cadence5
    • Momentum29 / 100 · weight 14%
      • Stars gained, relative to size49
      • Stars gained, absolute24
      • 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 measured
        not published by the vendor it integrates
    Weighted mean of the five
    55.1
    × relevance: the keyword is declared here
    0.78
    × continuity: actively changing
    1.00
    × evidence: modest but real audience
    0.85
    Composite score
    36.5
  • 20

    Jira MCP

    SteadyNew
    namcpgem/gem-jira-mcp ↗

    Best for: Teams running Jira Server/Data Center that need an AI assistant to read and write tickets, comments, worklogs, sprints, and links via direct REST API v2.

    Jira MCP exposes 17 tools for Jira Server/Data Center through REST API v2, covering ticket retrieval, JQL search, creation and updates, status transitions, comments, issue links, release notes, worklogs, watchers, and sprint moves. It assumes a Jira Server/Data Center account with username and password and Node.js 18+, configured through JIRA_HOST, JIRA_USERNAME, and JIRA_PASSWORD.

    GitHub stars
    2
    Stars over the last 90 days: 1 at the earliest of 14 readings and 2 at the latest, up 1.
    Stars / 30 days
    +1
    npm / typical week
    56
    PyPI / typical week
    no attributed package
    Tools exposed
    17
    Last commit
    12 days ago
    Commits / 12 weeks
    28
    Weekly commits over the last 12 weeks, oldest first: 4, 4, 2, 0, 0, 0, 0, 0, 0, 11, 7, 0. 28 in total, and the last figure is the current week so far.
    Maintenance grade
    A
    Tool descriptions
    A
    Score 33.4: show every number behind it
    • Adoption39 / 100 · weight 40%
      • GitHub stars12
      • npm downloads37
        downloads capped: not corroborated by repository audience
      • Used through Glamanot measured
        not 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 size38
      • Stars gained, absolute15
      • npm download trend14
    • Tool quality73 / 100 · weight 13%
      • Tool description quality65
      • 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.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

Questions people ask

Should I start with MCP Atlassian or Atlassian Rovo MCP Server for Jira Cloud?

Both work against Atlassian Cloud. MCP Atlassian is the community server: 6,014 stars, 97 stars gained per 30 days, a commit 29 days ago, and documented JQL search plus jira_create_issue, jira_update_issue and jira_transition_issue. Atlassian Rovo MCP Server is the official cloud-hosted bridge and reaches Jira, Confluence, Jira Service Management, Bitbucket, Compass and Loom, with 1,105 stars, 54 stars gained per 30 days and a commit 11 days ago. Pick MCP Atlassian when Jira issue work is the whole job, and Atlassian Rovo MCP Server when you need the other Atlassian products through one hosted endpoint.

Two servers are called MCP Atlassian. Which one do I want?

MCP Atlassian (sooperset/mcp-atlassian) is the Atlassian Cloud server for Jira and Confluence, with 6,014 stars, 97 stars gained per 30 days and a commit 29 days ago. mcp-atlassian (SharkyND/mcp-atlassian) exposes 73 tools across Confluence, Jira, Bitbucket and Xray for Jira, its tool descriptions graded B, and it has 27 stars, a commit 9 days ago and 36 commits in the last 12 weeks. Take the first for Jira Cloud issue search and updates, and the second when you want the wider product set or Xray test results alongside Jira.

Atlassian Jira MCP Server has 15,369 npm downloads a week. Is it maintained?

By the figures, no: its last commit was 226 days ago, it has 0 commits in the last 12 weeks, and it is labelled Abandoned but popular. It still draws 15,369 npm downloads in a typical week, so download volume and upkeep do not move together here. It exposes GET, POST, PUT, PATCH and DELETE tools that take an API path, so your agent has to know the Jira REST API surface itself rather than call named Jira operations.

What does jira-easy-mcp require before it will run?

A plain username and password for a self-hosted Jira Server or Data Center instance rather than an API token: it uses HTTP Basic Authentication deliberately, for setups where tokens are disallowed. It covers issues, JQL search, transitions, comments, worklogs and sprints. It took a commit 4 days ago and has 38 commits in the last 12 weeks, and it ships as jira-easy-mcp on npm with 39 downloads in a typical week.

Which server can answer Jira questions from a local copy instead of the API?

gadak mirrors selected Jira projects and Confluence spaces into one local SQLite file and answers MCP reads from it: read-only SQL, full-text search across issues, comments and wiki pages, issue detail, and sprint and retro reads. It took a commit 0 days ago and has 2,235 commits in the last 12 weeks. The tools it describes are all reads, so expect no issue creation or updates from it.

How do I keep an agent from writing to Jira by accident?

Check what each server does with credentials. mcp-jira-scoped authenticates against api.atlassian.com using Atlassian's scoped API tokens, enforces the granted scopes server-side and defaults to read-only, with delete confirmation. Atlassian Jira MCP Server, by contrast, exposes GET, POST, PUT, PATCH and DELETE tools that take an API path, and jira-easy-mcp signs in with a username and password, so both act through whatever credentials you hand them. Scope those credentials to what you actually want the agent to change.

Other comparisons