Skip to main content
Glama
Sign In
namcpgem

Jira MCP

by namcpgem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Jira MCP

No user-submitted related servers found.

    Related Servers

    • jira-easy-mcp

      IamSAL
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents work with self-hosted Jira Server/Data Center 7-10 using a plain username + password, no API tokens. 42 tools for issues, JQL search, transitions, comments, worklogs and sprints.
      89 npm
      4
      ISC

    • MCP Jira

      amruthabesto28
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.
      MIT

    • jira-mcp

      thammarongg
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to access and manage Jira boards, sprints, epics, issues, JQL searches, transitions, comments, worklogs, projects, users, and any REST endpoint across Jira Cloud and Data Center.
      43
      25 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose by resource and action: tickets, comments, worklogs, links, watchers, attachments, and sprints are separated cleanly. The few potentially overlapping areas, such as get_ticket vs get_comment and update_ticket vs transition_ticket, are explicitly clarified in the descriptions.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, including add_comment, create_ticket, update_worklog, remove_watcher, and generate_release_notes. There are no mixed conventions or vague standalone verbs.

    Tool Count4/5

    The 19 tools cover a broad Jira surface and each seems purposeful, but the count is slightly high relative to a typical well-scoped MCP server. The subresource operations for comments, worklogs, watchers, links, and attachments justify most of the size.

    Completeness4/5

    Core ticket workflows are well covered: create, get, search, update, transition, comments CRUD, links add/remove, worklogs create/update/delete, watchers add/remove, and sprint moves. Minor gaps remain, such as no ticket deletion, limited attachment operations beyond upload, and no sprint/project discovery tooling, but most can be worked around or are less common.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources