Skip to main content
Glama
ccampora

Jira Data Center MCP Server

by ccampora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Jira Data Center MCP Server

No user-submitted related servers found.

    Related Servers

    • Jira Cloud MCP Server

      aaronsb
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.
      195 npm
      4
      MIT

    • jira-mcp

      Soundhannes
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Jira Server/Data Center, enabling issue management, comments, attachments, JQL search, and more through natural language.
      -

    • Jira MCP Server

      AlexVulaj
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for integrating with Jira Server instances, enabling natural language interactions to create, update, search, and manage issues and comments.
      60 npm
      1
      MIT

    • Work Integrations MCP

      NazarKY
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.
      408 npm
      MIT
    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

    A3.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, such as issue retrieval, comment management, and workflow transitions. However, search_issues and execute_jql both run JQL queries with only a difference in field selection, and create_jira_story_from_requirements overlaps with create_issue for issue creation, requiring careful reading of descriptions to choose correctly.

    Naming Consistency4/5

    Names generally follow a get_/create_/add_/transition_ verb-noun pattern, making the set predictable. Minor deviations include server_info (lacking the 'get_' prefix) and transition_issue (using the verb 'transition' rather than a noun like 'issue_transition'), but these are still clear and do not confuse the overall convention.

    Tool Count5/5

    With 13 tools, the server covers a broad range of Jira operations without being overwhelming. Each tool addresses a meaningful capability, from basic issue CRUD-like operations to search, transitions, remote links, and a novel requirements-to-story transformer, fitting well within the typical 3-15 range.

    Completeness3/5

    The tool set lacks update_issue and delete_issue, which are fundamental for full issue lifecycle management. While it provides create, read, transition, comments, search, and project listing, an agent cannot modify an existing issue's fields or remove it, leaving a notable gap for many Jira workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources