Integration

TestRail integration

Test management platform API for organizing test cases, runs, results, and milestones across QA projects. Manage projects, suites, sections, test cases, runs, plans, milestones, and report results from automated test executions. Build CI/CD integrations, custom reporting dashboards, and automation pipelines that push pass/fail outcomes back to TestRail.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in TestRail.Built from the 29 TestRail tools below, on the connection you add once.

Common TestRail use cases

  • release planning
  • fixing typos at scale
  • onboarding a new product
  • resolving suite metadata
  • ending a regression cycle
  • cleaning up obsolete tests
  • browsing the test case tree
  • cleaning up accidental runs
  • cleaning up obsolete suites
  • cleaning up sandbox projects

What you can do with TestRail

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Case, 5 operations

  • add_caseAdd casePOSTCreates a new test case inside a section with optional template, priority and steps.
  • delete_caseDelete casePOSTPermanently deletes a test case.
  • get_caseGet caseGETRetrieves the full payload of a single test case by ID.
  • get_casesGet casesGETLists test cases of a project/suite with optional priority, type, milestone and date filters.
  • update_caseUpdate casePOSTUpdates the title, type, priority, steps, or other fields of an existing test case.

Project, 5 operations

  • add_projectAdd projectPOSTCreates a new TestRail project with a chosen suite mode.
  • delete_projectDelete projectPOSTPermanently deletes a TestRail project and all its data.
  • get_projectGet projectGETRetrieves the full configuration of a single TestRail project by ID.
  • get_projectsGet projectsGETLists all available TestRail projects, optionally filtered by completion status.
  • update_projectUpdate projectPOSTUpdates a TestRail project's name, description, or completion state.

Run, 5 operations

  • add_runAdd runPOSTCreates a new test run, either covering all suite cases or a specified subset.
  • close_runClose runPOSTCloses a test run and archives its final results.
  • delete_runDelete runPOSTPermanently deletes a test run and all its results.
  • get_runGet runGETRetrieves a single TestRail run with progress counters.
  • get_runsGet runsGETLists test runs of a project, optionally filtered by milestone, suite or completion.

Suite, 4 operations

  • add_suiteAdd suitePOSTCreates a new test suite inside a multi-suite TestRail project.
  • delete_suiteDelete suitePOSTPermanently deletes a test suite and all its descendant data.
  • get_suiteGet suiteGETRetrieves a single TestRail test suite by ID.
  • get_suitesGet suitesGETLists all test suites belonging to a TestRail project.

Section, 3 operations

  • add_sectionAdd sectionPOSTCreates a new section (folder) under a project or suite.
  • delete_sectionDelete sectionPOSTPermanently deletes a section and its descendant cases.
  • get_sectionsGet sectionsGETLists test case sections (folders) inside a TestRail project or suite.

Milestone, 2 operations

  • add_milestoneAdd milestonePOSTCreates a new milestone with optional due / start dates and parent.
  • get_milestonesGet milestonesGETLists milestones for a project with optional started/completed filters.

Result, 2 operations

  • add_result_for_caseAdd result for casePOSTRecords a pass/fail/blocked/retest result for a single case in a run.
  • get_results_for_caseGet results for caseGETLists historical test results for a single case in a run.

Status, 1 operation

  • get_statusesGet statusesGETLists all built-in and custom test statuses available in the TestRail instance.

Test, 1 operation

  • get_testsGet testsGETLists all tests inside a run, optionally filtered by status.

User, 1 operation

  • get_usersGet usersGETLists TestRail users, optionally scoped to a project for non-admin callers.

Use TestRail from Claude Code, Cursor or Codex

Connect TestRail in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TestRail operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect TestRail

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect TestRail once

    Add your TestRail connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

TestRail integration FAQ

What can you do with the TestRail integration?

LiveContext exposes 29 operations on TestRail, covering case, project, run and suite. Common uses include release planning, fixing typos at scale and onboarding a new product.

Popular integrations

Browse the whole catalog