- Home
- MCP servers
- Testomat.io
Testomat.io
- javascript
5
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"testomatio-mcp": {
"command": "npx",
"args": [
"@testomatio/mcp@latest",
"--token",
"<your-token>",
"--project",
"<project-id>"
],
"env": {
"TESTOMATIO_BASE_URL": "https://app.testomat.io",
"TESTOMATIO_API_TOKEN": "<your-token>"
}
}
}
}You can run and use the Testomat.io MCP Server to connect Testomat.io APIs with AI assistants, enabling you to query tests, suites, runs, plans, and more directly from your assistant interface.
How to use
Launch the MCP server using a local runtime so your AI assistant can access Testomat.io data and actions. Provide your API token and project identifier to authorize and scope requests. You can also set a base URL if you operate a self-hosted or alternative Testomat.io instance.
How to install
Prerequisites: Install Node.js 18 or higher to ensure built‑in fetch support, and have a package manager available (npm or yarn). You also need a Testomat.io account with API access.
Install and run the MCP server directly with npx using a simple command that passes your token and project identifier.
Configuration and usage with a Cursor client
To use the MCP server with Cursor, configure a Cursor MCP entry that runs the MCP server through npx and passes your token and project ID. You can also provide the token via environment variables.
{
"mcpServers": {
"testomatio": {
"command": "npx",
"args": ["@testomatio/mcp@latest", "--token", "<your-token>", "--project", "<project-id>"]
}
}
}
Environment variable approach
You can set environment variables for the API token and optional base URL, then run the MCP server with just the project ID.
export TESTOMATIO_API_TOKEN=<your-token>
export TESTOMATIO_BASE_URL=https://app.testomat.io # optional, defaults to https://app.testomat.io
npx @testomatio/mcp@latest --project <project-id>
Available tools
get_tests
Fetches all tests with optional filters such as plan, query, state, suite_id, tag, and labels via GET /tests.
get_test
Retrieves a single test by its ID, including details like labels, tags, and metadata via GET /tests/{test_id}.
search_tests
Searches tests using query parameters like query, tql, labels, state, priority, filter, and page via GET /tests.
create_test
Creates a new test with fields such as suite_id, title, description, code, file, state, tags, jira_issues, assigned_to, labels_ids, and fields via POST /tests.
update_test
Updates an existing test by test_id with fields such as suite_id, title, description, code, file, state, tags, jira_issues, assigned_to, labels_ids, and fields via PUT /tests/{test_id}.
search_suites
Searches for suites by query, labels, state, priority, and page via GET /suites.
get_root_suites
Lists root-level suites with no parameters via GET /suites.
get_suite
Retrieves a single suite by suite_id via GET /suites/{suite_id}.
create_suite
Creates a new suite with title, description, parent_id, and fields via POST /suites.
create_folder
Creates a new folder with title, description, parent_id, and fields via POST /suites.
get_labels
Fetches all available labels with their IDs and configurations.
create_label
Creates a new label with optional custom field and configuration.
unlink_label
Removes a label from a test or a suite.
get_runs
Lists all runs via GET /runs.
get_run
Gets a single run by run_id with optional tree view via GET /runs/{run_id}.
get_testruns
Fetches runs for a specific test by test_id via GET /testruns.
get_plans
Lists all plans with optional detail, labels, and page parameters via GET /plans.
get_plan
Retrieves a single plan by plan_id via GET /plans/{plan_id}.