Skip to main content
Glama
judexzhu

mcp-jira

by judexzhu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-jira

No user-submitted related servers found.

    Related Servers

    • Jira MCP OAuth gateway

      Wasim-Shaikh25
      F
      license
      B
      quality
      C
      maintenance
      MCP server that connects AI assistants to your Jira site, supporting PAT or SSO authentication for search, read, create, update, and delete operations on issues.
      17
      507 npm
      -

    • jira-mcp

      Pandacli
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.
      MIT

    • jira-mcp-ai

      IvanBBaev
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Jira Cloud that lets AI agents search, read, and write Jira issues using your own Atlassian account and API token, with write operations gated behind explicit opt-in.
      52
      5 npm
      MIT

    • mcp-jira-server

      dev-pradeep-singh
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides AI assistants with access to Jira Cloud for issue management, search, and workflow operations.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: search, get, create, update, transition, and metadata. No overlap exists; search returns lists while get returns single issue details, and transition handles workflow state changes.

    Naming Consistency5/5

    All tool names follow the jira_verb_noun pattern consistently (jira_search_issues, jira_get_issue, etc.). The one compound verb 'get_create_meta' still follows the verb_noun convention.

    Tool Count5/5

    Six tools cover the core Jira issue lifecycle without being excessive. The count is well-scoped for a focused issue management server.

    Completeness4/5

    Core CRUD and workflow transitions are covered: search, get, create, update, transition, and create metadata. Minor gaps include no delete issue or dedicated comment tool, but comments can be added via update/transition.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources