Skip to main content
Glama

Related Servers

Alternatives to Jira MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with self-hosted Jira instances via Personal Access Token, supporting issue management and project operations through natural language.
      54 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with self-hosted Jira instances using Personal Access Token authentication, letting users create, read, update, delete, and transition issues, search with JQL, and manage comments, assignments, projects, and issue types. Also supports fetching the current user's information and configuring custom fields and User-Agent headers for reverse-proxy setups.
      12
      478 npm
      1
      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
      2,853 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Atlassian Jira via API token authentication, with 46 optimized tools across modular architecture for CRUD, agile, dashboard, and search operations.
      33 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      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
      3 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific Jira resources and actions, but there is some overlap between jira_create_issue/jira_create_issue_advanced and jira_update_issue/jira_update_issue_advanced, which could cause confusion about when to use the advanced versions. The descriptions help clarify that advanced versions support more fields, but the distinction might not be immediately obvious to an agent.

    Naming Consistency5/5

    All tools follow a consistent jira_verb_noun pattern with snake_case, making them predictable and easy to parse. The naming convention is uniform across all 27 tools, with no deviations in style or structure.

    Tool Count3/5

    With 27 tools, the count is on the high side for a typical MCP server, bordering on heavy. While Jira is a complex system with many operations, some tools like jira_get_priorities or jira_get_statuses might be considered auxiliary, potentially making the set feel bloated compared to more streamlined servers.

    Completeness5/5

    The tool set provides comprehensive coverage for Jira operations, including full CRUD for issues (create, get, update, delete), metadata discovery (get_create_meta, get_edit_meta), search capabilities, user and project management, and workflow actions like transitions and linking. There are no obvious gaps, and the advanced tools ensure support for custom fields and complex scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues