Skip to main content
Glama
vuphuongminh

MCP Jira Server

by vuphuongminh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Jira Server

No user-submitted related servers found.

    Related Servers

    • jira-mcp-server

      TTranchese
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with self-hosted Jira instances via Personal Access Token, supporting issue management and project operations through natural language.
      226 npm
      Apache 2.0

    • MCP Jira Server

      apo100l
      A
      license
      A
      quality
      B
      maintenance
      Enables natural-language interaction with self-hosted Jira through the Jira REST API, supporting PAT or browser-cookie/SSO authentication. It allows viewing and managing issues, projects, comments, assignments, and statuses, as well as JQL search and issue creation/deletion.
      12
      393 npm
      MIT

    • Jira MCP Server

      pdogra1299
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira Cloud instances for comprehensive issue management including creating, updating, searching issues, managing comments, workflow transitions, and project metadata discovery. Supports JQL queries, user search, and custom field operations with secure API token authentication.
      12
      1,043 npm
      8
      MIT

    • 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
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation: get vs search vs create vs update vs delete for issues, plus separate comment, project, issue type, assignment, and user tools. The singular/plural distinction between get_project and get_projects is clear from context, and no two tools overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent jira_ prefix with a verb_noun snake_case pattern (e.g., get_issue, create_issue, add_comment). The convention is predictable throughout, with no deviations.

    Tool Count5/5

    12 tools is well-scoped for a Jira server, covering core issue CRUD, comments, projects, issue types, assignment, and user lookup without inflating the surface with redundant operations.

    Completeness4/5

    Core issue lifecycle (create, read, update, delete) and comment read/write are covered, but notable gaps exist for workflow transitions (changing status), attachments, issue links, and comment update/delete. These gaps are manageable for basic use but could cause failures for status-change workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources