Skip to main content
Glama
Mammals-at-work

mcp-xray

by Mammals-at-work
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-xray

No user-submitted related servers found.

    Related Servers

    • Xray MCP Server

      c4m3lblue-star
      A
      license
      B
      quality
      D
      maintenance
      Enables integration with Xray Cloud APIs for comprehensive test management including creating and managing test cases, test executions, test plans, and test sets. Supports CI/CD automation and test result tracking through GraphQL APIs.
      23
      30 npm
      3
      ISC

    • 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
      -

    • 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.
      16 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

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: connection check, GraphQL query, import results, and CRUD operations for test executions and test plans. There is no overlap or ambiguity between tools.

    Naming Consistency4/5

    Most tools follow the consistent xray_verb_noun pattern (e.g., get_test_plan, search_test_executions, create_test_execution). The exception is xray_graphql, which breaks the verb_noun convention but is still identifiable.

    Tool Count5/5

    With 9 tools covering connection, querying, importing results, and managing test executions/plans, the server is well-scoped. Each tool serves a clear purpose without over-fragmentation.

    Completeness3/5

    The server covers create, get, and search for both test executions and test plans, plus import and GraphQL queries. However, it lacks update and delete operations for these entities, which are common lifecycle operations and would require workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources