Skip to main content
Glama
denys-ispaniuk

TestRail MCP Server

by denys-ispaniuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to TestRail MCP Server

No user-submitted related servers found.

    Related Servers

    • TestRail MCP Server

      TenBarrel6
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact directly with TestRail instances for managing test projects, suites, cases, runs, results, plans, milestones, and attachments through the TestRail API with secure authentication.
      77
      137 npm
      1
      MIT

    • TestRail MCP Server

      Derrbal
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with TestRail test management systems through comprehensive API integration. Supports retrieving and updating test cases, projects, suites, runs, and results, plus adding attachments and managing test data through natural language commands.
      18
      12 npm
      MIT

    • TestRail MCP Server

      bun913
      A
      license
      A
      quality
      F
      maintenance
      Enables management of TestRail projects, test cases, runs, and results directly through MCP-supported clients. It provides a comprehensive set of tools to interact with the TestRail API for seamless test cycle management within AI environments.
      42
      1,101 npm
      44
      MIT

    • Testmo MCP Server

      filipljoljic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Testmo test management platform for creating, reading, updating, and deleting test cases, managing folders, and organizing test runs through natural language.
      4
      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 35 tools

    Disambiguation5/5

    Each tool targets a distinct entity and action (add, get, update, delete, close) with clear naming. Even multiple result tools are differentiated by context (case, run, bulk). No ambiguity.

    Naming Consistency5/5

    All tool names follow the verb_object pattern in snake_case (e.g., add_case, get_run, update_suite). Verbs are consistent and predictably used.

    Tool Count4/5

    35 tools is high but matches the complexity of TestRail’s domain (project, suite, section, case, run, result, milestone, plan). Most tools are necessary for comprehensive coverage.

    Completeness3/5

    Covers CRUD for cases, runs, suites, sections, and projects. However, milestones and plans only have get operations (no add/update/delete for milestones, no add/update for plans), which are notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources