Skip to main content
Glama
denis-platonov

qtm4j-mcp-server

by denis-platonov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to qtm4j-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
      29 npm
      MIT

    • zephyr-scale-mcp

      vilaabo
      A
      license
      A
      quality
      A
      maintenance
      MCP server for managing test cases, cycles, and results in Zephyr Scale on self-hosted Jira. Enables AI agents to create, search, update, and delete test artifacts through natural language.
      41
      45 npm
      MIT

    • qasphere-mcp

      Hypersequent
      A
      license
      A
      quality
      F
      maintenance
      QA Sphere MCP server that enables Large Language Models to interact directly with test management system test cases, supporting AI-powered development workflows and test case discovery.
      15
      78 npm
      23
      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.5/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Even similar operations like 'get_test_case' vs 'get_test_case_details' are differentiated by their descriptions and the level of detail returned. The three 'add_' tools target different entities (steps, cycle, folders), so no ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern with snake_case. Verbs like 'add_', 'create_', 'get_', 'list_', 'update_' are used appropriately, making the tool set predictable and easy to navigate.

    Tool Count5/5

    21 tools is well-scoped for a test management server. Each tool serves a specific function without overloading the user. The count is large enough to cover essential operations but not excessive.

    Completeness2/5

    The tool set lacks several obvious operations: no 'list_test_cycles' (only list test cases within a cycle), no delete tools for test cases, cycles, or folders, no 'remove_test_case_from_cycle'. These gaps could hinder agents from completing full workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources