Skip to main content
Glama
deanchong

testmonitor-mcp

by deanchong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to testmonitor-mcp

No user-submitted related servers found.

    Related Servers

    • Testing MCP

      shalonjovan
      A
      license
      Not graded
      quality
      D
      maintenance
      A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
      3
      GNU Lesser General Public v2.1 only

    • tcm-mcp

      JoinFullStackDev
      F
      license
      A
      quality
      B
      maintenance
      A stdio MCP server providing AI agents with a stable tool interface to read and write TCM test cases through REST, including search, CRUD operations, and a dry-run-to-commit safety flow.
      5
      -

    • testmo-mcp

      PeterAbah1819
      A
      license
      A
      quality
      C
      maintenance
      MCP server that integrates with Testmo to let AI assistants read projects, runs, results, and test cases, and create or update runs, results, and cases via natural language.
      15
      155 npm
      MIT

    • TestRail MCP Server

      uarlouski
      A
      license
      B
      quality
      A
      maintenance
      AI-native Model Context Protocol (MCP) server for TestRail. Lets Claude, Cursor, Windsurf, and other AI assistants browse projects, create and update test cases, kick off test runs, and record results through natural-language conversation — with strongly-typed tool schemas and per-project custom field validation that helps LLMs generate valid TestRail requests on the first try.
      27
      1,177 npm
      40
      Apache 2.0

    • zephyr-squad-server-mcp

      alejandroviera
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI agents to drive Zephyr for Jira (Server/Data Center) test management via ZAPI. It exposes operations for test cycles, folders, executions, test steps, step results, and ZQL search over stdio for use with any MCP client.
      40
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.6/5.0

    Scored across 173 tools

    Disambiguation3/5

    With 173 tools, many operations are near-identical across resource types (e.g., get_X_collection vs get_X, get_X_tags vs get_X_tags_collection), which can cause misselection without careful reading. Descriptions do distinguish them, but the sheer volume increases cognitive load and overlap risk.

    Naming Consistency4/5

    The dominant pattern is action_resource (get_application, post_issue, put_test_case, delete_webhook, restore_milestone) with batch and association variants, which is highly predictable. Minor deviations like 'my_account' (noun only) and mixed action verbs (open/close, archive/unarchive, mark_viewed) slightly break uniformity.

    Tool Count1/5

    173 tools is an extreme mismatch for a single MCP server, far exceeding practical bounds (typically 3-15) and likely to overwhelm an agent's selection process. The surface is excessively granular, with many near-duplicate operations across resources.

    Completeness4/5

    The server covers extensive CRUD lifecycles for core entities (applications, issues, projects, requirements, risks, teams, test cases, test runs, test results, users, webhooks, folders) including batch, restore, comments, attachments, and associations. Minor gaps exist for configuration entities like custom fields and test result states, which are read-only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources