Skip to main content
Glama
qamary666

jira-aio-mcp-server

by qamary666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jira-aio-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-xray

      Mammals-at-work
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Xray Cloud and Data Center for test management, including authentication, GraphQL queries, test execution/plan management, and result import via MCP.
      9
      10 npm
      MIT

    • rtm-mcp

      ngocdd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients to directly manage Jira Requirements and Test Management resources such as requirements, test cases, plans, executions, defects, tree structures, and automation via exposed tools.
      25 npm
      MIT

    • Xray MCP Server

      jithinjosejacob
      F
      license
      B
      quality
      F
      maintenance
      Enables AI assistants to interact with Xray Test Management for both Cloud and Server deployments. Supports test execution, importing results from multiple formats (JUnit, Cucumber, Robot Framework, TestNG), and managing test plans and executions.
      8
      3
      -

    • MCP Zephyr

      donyfs
      A
      license
      B
      quality
      D
      maintenance
      Enables comprehensive test management in Zephyr Scale Cloud, including creating and managing test cases, executing tests with step-by-step results, organizing test cycles and plans, and performing advanced JQL searches.
      18
      26 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: get vs search, projects vs folders vs test cases, and create vs update are clear. There is no meaningful overlap that would cause an agent to select the wrong tool.

    Naming Consistency3/5

    The tool naming is readable but inconsistent: four tools follow a get_aio_* pattern, while three use bare verb_noun forms like create_case and create_folder. This mix of conventions makes the set feel less unified, even though the verb and noun components are clear.

    Tool Count5/5

    Seven tools is well-scoped for an AIO test-case management server: project discovery, folder navigation, test-case search/retrieval, creation, and update are all represented. Each tool serves a clear purpose without redundancy.

    Completeness3/5

    The set covers project listing, folder handling, and test-case create/read/update/search, but there is no delete operation for either test cases or folders. This notable lifecycle gap prevents full end-to-end management of AIO test cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources