Skip to main content
Glama
Yogeshknaik

Jira Communication Server

by Yogeshknaik

Related Servers

Alternatives to Jira Communication Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Provides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.
      6
      6 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides Jira Cloud integration for AI agents, enabling them to search issues with JQL, retrieve detailed issue information, and create new tickets. It supports multiple Jira configurations and provides tools for managing attachments and comments through natural language.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Jira Cloud tickets, including listing, searching, creating, and updating issues through a set of MCP tools.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage Jira projects and issues using natural language, including creating, updating, searching issues, managing sprints, and more via the Jira API.
      36
      28 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.
      9
      5 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 11 tools

    Disambiguation5/5

    All tools have clearly distinct purposes: CRUD tickets, two attachment sources, project/status listing, JQL search, ticket retrieval by name&desc, assignee query, and assignment. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, with verbs like add, assign, create, delete, edit, execute, get, list, query. No mixing of styles.

    Tool Count5/5

    11 tools is well-scoped for a Jira server, covering essential operations without being bloated or insufficient.

    Completeness4/5

    Covers major CRUD for tickets, search, projects, statuses, assignments, and attachments. Missing a generic 'get_ticket' for full details and some lifecycle features like transitions or comment management, but still quite complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues