Skip to content
Testomat.ioTestomat.ioKnowledge Base

Why can't I connect to the Testomat.io MCP Server?

The connection issue is likely related to API access rather than the MCP client itself. Check the following:

  1. Verify your API token: Ensure the token is correct and hasn’t been revoked. MCP requests authenticate against the Public API v2.

  2. Use a project token, not a General token: The MCP server expects the project token (it starts with tstmt_) together with the Project ID. Both are on your project’s Settings → API Key page; the Project Reporting API key shown there is this token. A General token opens every project you have access to and isn’t what the MCP configuration expects.

  3. Review your MCP client configuration: Ensure your AI assistant or client is configured to point to the correct MCP server and that it passes the token and Project ID as configured. Example for Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "testomatio": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@testomatio/mcp@latest", "--token", "<TOKEN>", "--project", "<PROJECT_ID>"],
      "env": { "TESTOMATIO_BASE_URL": "https://app.testomat.io" }
    }
  }
}

Replace <TOKEN> and <PROJECT_ID> with your values. Claude Desktop uses the same configuration without the "type": "stdio" line. On the Tests page, ⋯ → MCP Server → Agents generates this configuration for you.

Treat the token like a password: it gives the assistant full access to the project. Never commit a config file that contains it.

If this doesn’t work

Section titled “If this doesn’t work”

If the connection issue persists, contact support via the live chat on testomat.io and provide the exact error message and setup details.

Section titled “Related documentation”
Section titled “Related articles”