Find anything in seconds
Ask for tests, suites or runs by name, tag, priority or status. No more clicking through folders and filters.
“Show me all high-priority tests in the Checkout suite”
“Which runs failed last week on staging?”
Open source · free
Testomat.io MCP for QA engineers
Your tests on call. Talk to them! Connect your AI assistant to Testomat.io once — then just ask. Find tests, start runs, understand failures. No clicking through menus, no commands to memorize.
Works in your assistant
Claude Code Cursor ChatGPT & more
What is this?
A bridge between your assistant and Testomat.io
MCP is just a secure connection. It lets Claude Code, Cursor or ChatGPT see and update your Testomat.io project — so you can work by chatting instead of clicking.
- 01
Connect once
Paste your Testomat.io project key into your AI assistant. That is the whole setup — no code, no plugins to learn.
- 02
Ask in plain words
Type what you want the way you would tell a colleague. “Show me flaky checkout tests” works. No commands to memorize.
- 03
It does the clicking for you
Your assistant opens, reads, creates and updates things in Testomat.io directly — and shows you what it did.
Claude Code · Testomat.io connected
Show me all high-priority checkout tests that failed this week
Found 6 tests. 3 failed twice in a row — “Apply discount code”, “Guest checkout” and “Card declined”. Want me to open a run with just these, or link them to JIRA-123?
Open a run with just these, on staging
✅ Run R-128 “Checkout hotlist” is ready on staging with 3 tests. Nothing else was touched.
This is the whole skill level required: describe the outcome, confirm, done.
Everyday ideas
What to ask for this week
Six starting points QAs use daily. Copy a phrase, paste it into your assistant, adjust the names — and watch it happen in Testomat.io.
Tidy up tests without the busywork
Create, rename, move or clean up tests and suites by just describing it. Great for release cleanup days.
“Create a suite called Smoke for release 2.4”
“Move all login tests into one suite”
Start and finish runs hands-free
Spin up a run for a plan or a set of suites, assign it, then close it — all from chat, while you keep testing.
“Start a smoke run for the Auth plan on staging”
“Finish the manual regression run”
Understand what failed and why
Pull results, compare runs, see which tests keep failing and what they are linked to — with links back to Testomat.io.
“What failed in yesterday’s nightly run?”
“Show results for the payment tests in run R-42”
Plan releases in one sentence
Build a test plan from a description: pick suites, tags or priorities and your assistant assembles it.
“Build a regression plan from all critical tests”
“Make a plan with everything tagged @checkout”
Keep bugs, files and docs attached
Link Jira issues, attach screenshots, connect requirements — so every test tells the full story.
“Link JIRA-123 to the login tests”
“Attach this screenshot to the failed checkout test”
Enterprise version · separate add-on
Answers for leads: where is quality going?
The Enterprise connection includes everything above, plus quality analytics. Ask about flakiness, trends and dashboards — your assistant reads the numbers and explains them in plain words.
@testomatio/mcp-enterprise
Install guide on GitHub
Spot flaky, slow and failing tests
Ask which tests waste your time: flaky ones, slowest ones, ones that never pass. Get the list with numbers.
“Which 10 tests are the flakiest in the last 30 days?”
See quality trends at a glance
Success rate, automation rate, results by day — your assistant reads your dashboards and explains them.
“How did our success rate change this month?”
Reuse your saved charts
Already saved charts in Testomat.io? Ask for their numbers or drill into the matching tests and runs.
“Show me results of my Smoke Health chart”
Needs the analytics feature enabled on your Testomat.io project. Not sure? Connect the standard version first — you can upgrade anytime without reconnecting.
Setup · about 5 minutes
Connect your assistant
You need two things from Testomat.io: a project token and a project ID (Settings → API). Then pick your assistant below — or skip setup entirely with Testeiya.
Claude Code
Run one command in your project folder
Run it once in your project folder. For Enterprise analytics, swap in @testomatio/mcp-enterprise.
claude mcp add testomatio -- npx -y @testomatio/mcp@latest --token <TOKEN> --project <ID> Cursor
Add to .cursor/mcp.json
Paste this into .cursor/mcp.json, then restart Cursor:
{"mcpServers": {"testomatio": {"command": "npx", "args": ["-y", "@testomatio/mcp@latest", "--token", "<TOKEN>", "--project", "<ID>"]}}} ChatGPT
Desktop app (Mac / Windows) · Plus / Pro
In the desktop app: Settings → Connectors → enable Developer Mode → add an MCP server, then paste this:
{"mcpServers": {"testomatio": {"command": "npx", "args": ["-y", "@testomatio/mcp@latest", "--token", "<TOKEN>", "--project", "<ID>"]}}} Or use a dedicated QA agent
Testeiya — our QA agent, already connected
Skip keys and JSON entirely. Testeiya has Testomat.io built in — open it and ask your first question right away. Best for QAs who just want answers, not configuration.
Full step-by-step with screenshots → github.com/testomatio/mcp
Capability reference
Everything your assistant can reach in Testomat.io
Grouped by area — click to expand. Enterprise analytics at the bottom.
Capability reference
Everything your assistant can reach in Testomat.io
Grouped by area — click to expand. Enterprise analytics at the bottom.
Standard · @testomatio/mcp
Tests
- Find tests by name, tag, priority or status
- Read a full test with steps and expected results
- Create, update, move or delete tests
Suites
- Browse the suite tree
- Create folders and group tests
- Rename, move or delete suites
- Attach files and link issues to suites
Runs
- List runs and filter by result or environment
- Start a run from tests, suites or a plan
- Assign, launch, finish or rerun a run
Results
- See every result inside a run
- Filter by passed, failed, skipped or pending
- Report a new result with message and time
Plans
- List release and regression plans
- Build a plan from suites, tests or a filter
- Update or hide a plan
Run groups
- Group runs into folders
- Pin important groups
- Reorganize the run view
Steps & snippets
- Reuse shared steps across tests
- Keep code snippets next to tests
- Create and update both from chat
Labels, tags & milestones
- List all labels and tags in the project
- Create labels for filtering and custom fields
- Read milestones and releases
Issues
- See linked bugs on any test, suite, run or plan
- Link a Jira issue or any URL
- Unlink issues that are no longer relevant
Attachments
- List files on tests, suites and results
- Upload a screenshot or log from a file path
- Delete outdated attachments
Requirements
- List requirements from Jira, Confluence, files or text
- Create requirements, including file uploads
- Update or delete requirements
Branches & project
- List and manage test branches
- Work on a branch without touching main
- Read project settings, environments and features
Enterprise · @testomatio/mcp-enterprise — adds analytics
Quality reports
- Flaky, slow, failing and never-executed tests
- Skipped tests, failures, defects and linked issues
- Filter by date range and environment
Trends
- Project and runs summaries
- Success rate and automation rate over time
- Results and priorities by day
Saved charts
- List your saved charts and queries
- Read any chart definition with its filters
- Get totals per chart, or drill into matching tests and runs
Technical names and parameters → full reference on GitHub
Questions QAs ask
No AI degree required
Do I need to know how AI works?
No. If you can chat, you can use this. You describe what you need in plain English — your assistant (Claude Code, Cursor or ChatGPT) talks to Testomat.io for you. There is nothing to program and no new interface to learn.
Will it change or delete my data without asking?
Your assistant always tells you what it is about to do and shows the result with a link back to Testomat.io. Reading is always safe. For anything that creates or changes data, ask it to confirm first — e.g. “show me before you change anything”. Every change is also grouped in Testomat.io history, so you can review it.
What is the difference between the two versions?
The standard version covers everyday QA work: finding, creating and organizing tests, suites, plans and runs, checking results, linking issues and attaching files. The Enterprise version adds everything from standard, plus quality analytics: flaky, slow and failing tests, success and automation trends, and your saved charts.
Do I need a special Testomat.io plan for analytics?
Yes — the analytics answers (flaky tests, trends, saved charts) need the analytics feature enabled on your Testomat.io project. If you are not sure, ask your workspace admin or try the standard version first; it works on any project.
Where do I find my project key and ID?
In Testomat.io, open your project → Settings → API. Copy the project token (the secret key) and the project ID. Paste them into the setup snippet below. Keep the token private, like a password — never share it in screenshots.
Does it work with branches?
Yes. If your project uses branches, just mention the branch name in your request — for example “on branch release-2.4”. Your assistant will look there first and never touch your main suite by accident.
Open source · free
Ask your first question today
Connect in 5 minutes, then paste one of the phrases above into Claude Code, Cursor or ChatGPT. Your tests are already waiting.