Skip to main content
Glama
albertor03

Jira QMetry MCP Server

by albertor03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Jira QMetry MCP Server

No user-submitted related servers found.

    Related Servers

    • QTM4J MCP Server

      salehrifai42
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes the QMetry Test Management for Jira Cloud REST API as tools for MCP-compatible clients. It enables users to manage test cases, test cycles, test executions, test plans, folders, and automation rules through natural language interactions.
      30
      32 npm
      MIT

    • jira-mcp

      nayzo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Jira Cloud tailored for ALM projects with Zephyr Scale integration, enabling issue management, sprint tracking, and test step operations.
      408 npm
      1
      MIT

    • Zephyr Scale MCP Server

      Milo0821
      A
      license
      B
      quality
      B
      maintenance
      An MCP server for Zephyr Scale test management supporting Jira Cloud and Data Center. It enables creating, reading, and managing test cases and test runs via the Atlassian REST API with official API-compliant schemas.
      16
      511 npm
      6
      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

    B3/5.0

    Scored across 93 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs (e.g., test case vs test cycle). However, the high number of similar patterns (e.g., multiple 'get-custom-field' variants) may cause occasional confusion, though descriptions help.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create-qmetry-test-case, get-qmetry-test-cycle). Even abbreviations like 'tc' and 'tcy' are used consistently across similar operations.

    Tool Count2/5

    93 tools is excessively high for a test management server. An agent would need to navigate an overwhelming list, making selection error-prone. A more focused set (20-40) would be appropriate.

    Completeness5/5

    The surface covers all major lifecycle operations for test cases, cycles, plans, folders, statuses, labels, steps, versions, linking, and custom fields. No obvious gaps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources