# 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