Skip to main content
Glama
uarlouski

TestRail MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TESTRAIL_API_KEYYesYour TestRail API key
TESTRAIL_USERNAMEYesYour TestRail user email address
TESTRAIL_INSTANCE_URLYesYour TestRail instance URL (e.g., https://example.testrail.io)
TESTRAIL_ENABLE_SHARED_STEPSNoSet to true to enable Shared Steps management toolsfalse

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
query_projectB

Retrieve a single project or all projects in TestRail. Set payload.action to 'one' or 'many' to specify the operation.

mutate_suiteA

Create a new test suite or update an existing one in TestRail. Set payload.action to 'create' or 'update' to specify the operation.

query_suiteA

Retrieve a single test suite or all test suites for a project in TestRail. Set payload.action to 'one' or 'many' to specify the operation.

get_caseA

Get detailed information about a test case including its custom fields

get_casesA

Get all test cases for a project. Filter by section, API params (priority, type), or any field including custom fields via 'where'. Returns case IDs, titles, and any additional requested fields.

get_case_fieldsA

Get the field schema for test cases for a specific project. You should normally provide project_id to get fields applicable to your project. If you truly need all fields across all projects, you may omit project_id, but this is rarely what you want. Returns available fields with their types and options (for dropdown fields).

update_caseA

Update a test case in TestRail. The update operation requires knowing valid field names that are returned by get_case_fields tool. Supports partial updates — only specify the fields you want to change.

update_casesA

Bulk update multiple test cases with the same field values. The update operation requires knowing valid field names that are returned by get_case_fields tool. More efficient than calling update_case multiple times.

add_caseA

Create a new test case in TestRail. The create operation requires knowing valid field names that are returned by get_case_fields tool.

get_sectionsA

Get all sections for a project. Returns section IDs and names that can be used with add_case

mutate_sectionA

Create a new section or update an existing section in TestRail. Set payload.action to 'create' or 'update' to specify the operation.

mutate_runA

Create a new test run or update an existing one in TestRail. Set payload.action to 'create' or 'update' to specify the operation.

query_runA

Retrieve a single test run or all test runs for a project in TestRail. Set payload.action to 'one' or 'many' to specify the operation.

add_attachment_to_runA

Add an attachment to a test run in TestRail. If the file_path points to a directory, it will be automatically zipped before uploading. Maximum upload size is 256MB.

add_resultsC

Add one or more test results to a test run

add_results_for_casesA

Add one or more test results to a test run using case IDs instead of test IDs

get_resultsB

Get results for a specific test in TestRail.

get_configurationsA

Get all configuration groups and configurations for a project in TestRail.

get_labelsA

Get all available test case labels (sometimes called tags) for a project. Returns label IDs and titles that can be used when creating or updating test cases.

get_prioritiesA

Get all available test case priorities (e.g. Critical, High, Medium, Low). Returns priority IDs and names that can be used when creating or updating test cases.

get_statusesA

Get all available test statuses (e.g. Passed, Failed, Blocked). Returns status IDs and names that can be used with add_result and get_tests

get_templatesA

Get available test case templates for a project. Template IDs determine which fields are available when creating or updating test cases

get_testsA

Get tests for a test run, optionally filtered by status

get_usersA

Get active users from TestRail. Resolves active users globally or per-project. If global fetch is forbidden (for non-admin accounts), falls back to merging users across all active projects so users referenced as reviewers or assignees can be resolved.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/uarlouski/testrail-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server