add_case
Add a new test case
LABSCO SUMMARY
A test run can be assembled, executed against and closed without anyone opening TestRail.
The set is deliberately flat CRUD, which makes it good for the loop a CI job actually needs: add_run against a case list, add_result per test as the suite reports, close_run at the end. Results go in one at a time — there is no batch result tool here — so a large suite means one call per test. Delete exists on every object type and takes only an id, so the credential that files results is also the credential that can remove a project.
What it is
A TestRail API client covering projects, test cases, runs, results and datasets, with read, create, update and delete on each.
What you get
- Projects read singly or in full, created with announcement and suite_mode, updated, marked completed, and deleted
- Test cases per project or suite, created and updated with title, separated steps, estimate, priority_id, type_id, milestone_id and refs
- Runs built from an explicit case_ids list or from include_all, assigned to a user, then updated, closed or deleted
- Results posted against a test with status_id, elapsed, defects, version, comment and assignee, and read back per test
- Datasets per project, created with name and description, renamed and deleted
Requirements
A TestRail instance and an account with API access, supplied as TESTRAIL_URL, TESTRAIL_USERNAME and TESTRAIL_API_KEY. That account's permissions are the only limit on the delete tools, which cover projects, cases, runs and datasets.
Setup effort
One command plus a key — uvx testrail-mcp, then supply credentials
USE CASES
01
Standing up a regression run against tonight's build
Find the project, pull the cases for the suite you are covering, and open a run from an explicit case list or from every case in the suite, assigned to whoever is on duty.
02
Reporting results back as the suite finishes
Post a result per test with status, elapsed time and any defect references, read them back to confirm what landed, and close the run so it stops accepting entries.
03
Keeping the case library in step with code that has moved on
Open the case, rewrite its separated steps, estimate or priority, and delete the ones covering behaviour that no longer exists.
04
Setting up a new project so a team can start filing against it
Create the project with its suite mode and announcement, adjust it once the shape settles, and add the datasets the cases will draw on.
23 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_dataset
Add a new dataset
add_project
Add a new project
add_result
Add a new test result
add_run
Add a new test run
close_run
Close an existing test run
delete_case
Delete a test case
delete_dataset
Delete a dataset
delete_project
Delete a project
delete_run
Delete a test run
get_case
Get a test case by ID
get_cases
Get all test cases for a project/suite
get_dataset
Get a dataset by ID
get_datasets
Get all datasets for a project
get_project
Get a project by ID
get_projects
Get all projects
get_results
Get all test results for a test
get_run
Get a test run by ID
get_runs
Get all test runs for a project
update_case
Update an existing test case
update_dataset
Update an existing dataset
update_project
Update an existing project
update_run
Update an existing test run
BEFORE YOU INSTALL
What to know first
Tools you get
23 tools when we connected. The server can delete projects, cases, runs and datasets without asking twice; results can be added but not updated or deleted, and close_run is one-way. Use an API key scoped to what it should touch.
Requires
- uvx on PATH
- TESTRAIL_URL in your environment
- TESTRAIL_USERNAME in your environment
- TESTRAIL_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 23 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx testrail-mcpMCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"testrail": {
"command": "uvx",
"args": [
"testrail-mcp"
],
"env": {
"TESTRAIL_URL": "https://<YOUR_INSTANCE>.testrail.io",
"TESTRAIL_USERNAME": "<YOUR_TESTRAIL_USERNAME>",
"TESTRAIL_API_KEY": "<YOUR_TESTRAIL_API_KEY>"
}
}
}
}Cursor, Windsurf
JSON
{
"mcpServers": {
"TestRail MCP": {
"command": "uvx",
"args": [
"testrail-mcp"
],
"env": {
"TESTRAIL_URL": "https://<YOUR_INSTANCE>.testrail.io",
"TESTRAIL_USERNAME": "<YOUR_TESTRAIL_USERNAME>",
"TESTRAIL_API_KEY": "<YOUR_TESTRAIL_API_KEY>"
}
}
}
}
