How to utilise testRigor’s MCP server
 |
Set up
Generating PAT
In order to access the MCP feature we must generate a PAT token, to do so first we require to access testRigor’s app homepage, click our username, then click “API Tokens”.
Once we’re PAT page we must click on on the click “Generate a new token”.
Once the PAT has been successfully generated all that is left is to do is to properly configure the MCP server on the target MCP-compatible tool, below we’ll show how to perform this configuration on Claude code and Cursor.
Configuration using Claude Code
For Claude Code we must issue the following command on the command line:
claude mcp add --transport http testrigor https://api2.testrigor.com/api/v1/mcp --header "personal-access-token: <your-token>" -s user
After that, you can run claude then start making queries, for example list all the test suites:
claude
▗ ▗ ▖ ▖ Claude Code v2.1.140
Opus 4.7 (1M context) with xhigh effort · API Usage Billing
▘▘ ▝▝
❯ /mcp
⎿ MCP dialog dismissed
❯ list all my test suites in testrigor
Called testrigor (ctrl+o to expand)
⏺ Here are your testRigor test suites (50 total):
┌─────┬───────────────────────────────────┬───────────────────────────────┐
│ # │ Name │ Type │
├─────┼───────────────────────────────────┼───────────────────────────────┤
│ 1 │ my first test suite 01 │ WEB_DESKTOP_CHROME_WINDOWS_10 │
├─────┼───────────────────────────────────┼───────────────────────────────┤
│ 2 │ TestRigor Table │ WEB_DESKTOP_CHROME_MAC │
├─────┼───────────────────────────────────┼───────────────────────────────┤
│ 3 │ Test Case Training Tests │ WebDesktopChrome │
├─────┼───────────────────────────────────┼───────────────────────────────┤
...
Configuration using Cursor
To set up the MCP server on Cursor we must go to Cursor settings, then click on “Add Custom MCP”:
The file “mcp.json” will open, we must update it as follows:
{
"mcpServers": {
"testrigor": {
"url": "https://api2.testrigor.com/api/v1/mcp",
"headers": {
"personal-access-token": ""
}
}
}
}
Once that has been done you should be able to see testRigor listed under “Installed MCP Servers”. You should now be able to start making queries.
Available tools
The testRigor MCP server provides these following tools:
- List test suites: this will provide a list of all the test suites that were made.
- Get test suite: this tool will provide the details for a specific test suite in particular.
- List test cases: this will list the test cases that are contained inside a test suite.
- Get test case: used to extract specific information about a particular test case (the description, UUID, steps, etc).
- List test case runs: this will list all the test suite runs that were performed on a particular test suite.
- Run test cases & Get run: you can use this to list the test cases that you wish to run in a particular test suite then get their status after the run is finished.
- Run green regressions: used to run only those test cases that were previously marked as passed.
- Execute supplied test steps: this will execute test steps on a given test suite.
- List run test cases: it will provide a list of all the test cases that were ran on a particular test suite run.
- List run failures: will only provide the failures that occurred on a given test suite run.
- Get execution details: this will show the the execution details for a particular test case, detailing what action was performed on each step.
- List runs: this will provide a list of all the test suite runs that were performed on a particular test suite.
- Get run: This will provide specific information about a test suite run (Status, Branch, App URL, time created, etc).
- Cancel task: this will abort any tasks (test suite runs, test case executions) that are currently in progress.
Usage example on Claude code
Having already configured our MCP server we could issue queries as follows:
check the execution status for the last test case in this suite
Then we’ll get the detailed output of each action that was performed on that test case:
Execution details for live-session-1779808877753 — the only test case in the latest Support learning run (evMtjzQP5qjxw9g9C, 2026-05-26, 16m 49s total, Failed). This was clearly a live-session / interactive exploration, not a normal scripted test — 37 steps, many retries of the same action against a PDF in the browser (api.printnode.com/.../multipage.pdf). ┌──────┬──────────────────────────────────────────────────────────┬────────────────────────────────────────────┐ │ Step │ Description │ Status │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 1 │ (init) │ ✓ │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 2 │ open url ".../multipage.pdf" │ ✓ │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 3 │ (load) │ ✓ │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 4 │ click exactly "1" using OCR only │ ❌ Can't find button '1' │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 5 │ click exactly "1" using OCR only using the mouse │ ❌ Can't find button '1' │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 6 │ click "1" using OCR only using the mouse │ ✓ │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 7 │ (post-click) │ ✓ │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 8 │ click exactly "1" using OCR only using the mouse │ ❌ Can't find button '1' │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 9 │ scroll down using the mouse until page contains "7" │ ✓ │ │ │ using OCR only │ │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤ │ 10 │ enter "7" into "pageSelector" │ ❌ Can't find input 'pageSelector' │ │ │ │ (CRITICAL) │ ├──────┼──────────────────────────────────────────────────────────┼────────────────────────────────────────────┤
You're 15 Minutes Away From Automated Test Maintenance and Fewer Bugs in Production
Simply fill out your information and create your first test suite in seconds, with AI to help you do it easily and quickly.
| Achieve More Than 90% Test Automation | |
| Step by Step Walkthroughs and Help | |
| 14 Day Free Trial, Cancel Anytime |
“We spent so much time on maintenance when using Selenium, and we spend nearly zero time with maintenance using testRigor.”
Keith Powe VP Of Engineering - IDT
