Skip to main content
Glama
Sign In
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
      D
      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

    • @g-tiwari/mcp-testrail

      g-tiwari
      A
      license
      C
      quality
      C
      maintenance
      MCP server for TestRail API, providing AI assistants with 107 tools to manage test cases, runs, results, plans, and more. Supports API key, password, and SSO cookie authentication.
      54
      14 npm
      2
      MIT

    • testmo-mcp

      PeterAbah1819
      A
      license
      A
      quality
      D
      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
      50 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.3/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (query vs mutate vs case/result operations). However, get_tests is explicitly deprecated in favor of query_test, creating a duplicate path, and add_results vs add_results_for_cases are similar enough to require careful selection.

    Naming Consistency3/5

    There are three parallel naming schemes: query_/mutate_ with action payloads for resources, get_/add_/update_ for cases and results, and get_ for reference data. Each is readable, but the mixed verb conventions for similar operations make the set less predictable.

    Tool Count3/5

    27 tools is on the heavy side for an MCP server, though TestRail is a broad domain with many entities. The count is inflated by a deprecated duplicate (get_tests) and multiple result-adding variants, so some consolidation would help.

    Completeness3/5

    Read and write coverage is strong across projects, suites, sections, cases, runs, tests, results, attachments, and reference data. However, delete operations are absent across nearly all resources, and project mutation (create/update/delete) is missing, leaving notable lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources