io.github.tesults/tesults-mcp
Ask your AI agent why your tests are failing. Instant analysis on failures and regressions.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
tesults-mcpclaude mcp add tesults-mcp -e 'TESULTS_API_TOKEN=<your tesults_api_token>' -e 'TESULTS_READ_ONLY=false' -- npx -y tesults-mcp@1.1.0
{
"mcpServers": {
"tesults-mcp": {
"command": "npx",
"args": [
"-y",
"tesults-mcp@1.1.0"
],
"env": {
"TESULTS_API_TOKEN": "<your tesults_api_token>",
"TESULTS_READ_ONLY": "false"
}
}
}
}
Environment variables
TESULTS_API_TOKENrequired secret Tesults API token - obtain from your Tesults project configurationTESULTS_READ_ONLYSet to true for reporting-only mode: only the reporting and insight tools are exposed and non-GET API requests are blocked locally
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
tesults-mcp
Tesults MCP server. Connect AI agents and MCP-compatible tools to your Tesults test results, insights, and targets.
Documentation
Full setup and usage documentation: https://www.tesults.com/docs/api/mcp
Quick start
claude mcp add tesults-mcp npx tesults-mcp -e TESULTS_API_TOKEN=your-api-token
Reporting-only mode
Set TESULTS_READ_ONLY=true in the MCP server's environment alongside
TESULTS_API_TOKEN. This exposes only the seven reporting and insight tools.
Target creation, editing, deletion and token regeneration are not registered,
and non-GET API requests are blocked locally.
Existing configurations remain unchanged when this setting is omitted or false.
This is a restriction in this MCP server, not a reduction in the API token's
permissions. Keep the token private. Insight tools can still generate and cache
AI analyses on the server; they do not change your test results or targets.
Requests time out after 60 seconds and responses are limited to 10 MiB.
For large result sets, request fewer runs or use cases=false for summaries.
API failures are returned as tool errors, not successful answers.
These options apply to this source version and require an updated installation once released. They do not change an already installed published package.
Offline checks
Run node --test tests/hardening.test.js. Tests do not call Tesults or use a real token.
License
MIT
Frequently asked questions
What is io.github.tesults/tesults-mcp?
Ask your AI agent why your tests are failing. Instant analysis on failures and regressions.
How do I install io.github.tesults/tesults-mcp?
It runs on your machine. In Claude Code: claude mcp add tesults-mcp -e 'TESULTS_API_TOKEN=<your tesults_api_token>' -e 'TESULTS_READ_ONLY=false' -- npx -y tesults-mcp@1.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.tesults/tesults-mcp need an API key?
Yes. It expects TESULTS_API_TOKEN, which you set in its configuration.
Is io.github.tesults/tesults-mcp open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.tesults/tesults-mcp?
It is published by tesults. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.