Skip to main content
Glama
imrnbeg

Jira MCP Server

by imrnbeg

Related Servers

Alternatives to Jira MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      D
      maintenance
      Connects Jira with Claude, enabling users to search issues, view issue details, update issues, add comments, and retrieve project information through natural language commands.
      1
      30 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.
      135 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants like Claude to Jira projects, enabling natural language queries and operations for issue management, project tracking, comments, and workflows through the Jira REST API.
      11,401 npm
      74
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jira for managing projects, issues, tasks, and workflows through the Model Context Protocol, allowing users to delegate PM tasks through Claude Desktop.
      25 npm
      64
      MIT
    • 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,883 npm
      8
      MIT

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Jira resources and actions. There is no overlap between tools like get_jira_issue (single issue details), list_project_issues (project-specific listing), and search_jira_issues (general JQL search), making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable with verbs like 'get', 'list', and 'search' clearly indicating the action type, and nouns specifying the target resource (e.g., jira_issue, project, boards).

    Tool Count5/5

    With 10 tools, this server is well-scoped for Jira operations, covering core workflows like issue retrieval, project management, and board/sprint handling. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness3/5

    The toolset provides strong read/search capabilities but has notable gaps in write operations. There are no tools for creating, updating, or deleting issues, comments, or other resources, which limits agents to read-only workflows and may cause failures in scenarios requiring modifications.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues