Skip to main content
Glama
uarlouski

TestRail MCP Server

by uarlouski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to TestRail MCP Server

No user-submitted related servers found.

    Related Servers

    • TestRail MCP Server

      sker65
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that allows interaction with TestRail's core entities (projects, cases, runs, results, datasets) through a standardized protocol compatible with MCP clients like Claude Desktop.
      23
      20
      MIT

    • testrails-mcp

      adakh3
      A
      license
      A
      quality
      D
      maintenance
      MCP server for TestRail that enables AI agents to manage test cases, runs, and results, plus a bundled skill to convert Jira tickets into TestRail test cases.
      15
      MIT

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

    B3.3/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools map to clearly distinct TestRail entities (cases, suites, sections, runs, results, attachments, reference data). The main overlap is add_results vs add_results_for_cases, which differ only in ID type, and the mixed query_/get_ prefixes make retrieval tools slightly harder to distinguish at a glance.

    Naming Consistency2/5

    The tool set mixes get_, query_, add_, update_, and mutate_ prefixes without a clear rule. mutate_section/mutate_suite/mutate_run bundle create/update behind an action parameter while cases use separate add_case and update_case tools, and there is no consistent singular/plural or CRUD convention.

    Tool Count2/5

    With 26 tools, the server is over-scoped; several reference-data getters could be consolidated and add_results/add_results_for_cases are near duplicates. This crosses the 25+ threshold and feels heavier than the core TestRail workflows require.

    Completeness2/5

    The set covers read/create/update for many entities but has no delete operations anywhere (cases, sections, suites, runs, attachments) and no way to close a run. It also lacks project creation/update, so cleanup and some lifecycle workflows will dead-end.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources