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
      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
      13 npm
      2
      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
      335 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (e.g., get_case vs get_cases, query_suite vs mutate_suite), and descriptions help resolve overlaps. However, the results tools (get_results, add_results, add_results_for_cases) and the deprecated get_tests vs query_test create some ambiguity that could lead to misselection.

    Naming Consistency4/5

    All tool names are snake_case with a verb_noun structure, which is largely predictable. Still, retrieval uses both get_ and query_, while writes use add_, update_, and mutate_ across similar resources, making the convention slightly inconsistent rather than uniform.

    Tool Count3/5

    27 tools is on the heavy side for an MCP server, though TestRail's broad domain (projects, suites, sections, cases, runs, tests, results, attachments, metadata) justifies many of them. Redundant entries like get_tests and two result-add variants keep the count from feeling fully earned.

    Completeness3/5

    Core read/create/update workflows for cases, suites, sections, runs, results, and attachments are present, so common test management tasks are covered. However, delete operations are entirely absent, and project, milestone, and plan management are not represented, leaving notable lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources