Skip to main content
Glama
valvacchs

TestRail MCP Server

by valvacchs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to TestRail MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      19 npm
      MIT

    • TestRail MCP Server

      denys-ispaniuk
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with TestRail test management system, supporting full CRUD operations on projects, suites, sections, test cases, runs, results, plans, and milestones.
      35
      1,138 npm
      1
      MIT

    • 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

      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
    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.2/5.0

    Scored across 42 tools

    Disambiguation5/5

    Each tool targets a distinct operation on a specific TestRail entity (e.g., case, run, plan, section). Overlapping tools like addCase vs addBdd are clearly differentiated by their purpose and input parameters. Descriptions provide sufficient detail to avoid confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun camelCase pattern (e.g., addCase, getSuite, deleteSection). Verbs are standardized (add, get, delete, update, copy, move), making the naming predictable and easy to navigate.

    Tool Count2/5

    With 42 tools, the server is far beyond the typical 3-15 range for a well-scoped set. While TestRail's feature set justifies many operations, the count feels excessive and could be consolidated (e.g., merging getCaseFields and getCaseTypes into a single tool).

    Completeness2/5

    The tool set covers core entities but has significant gaps: missing deleteRun, deletePlan, deleteSuite, deleteProject, updatePlan, updateProject, and any milestone management beyond retrieval. These omissions prevent full CRUD lifecycle coverage.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources