MCP server
The Testr MCP server exposes your owner workspace to any client that speaks the Model Context Protocol. Your agent can read campaign scope, private instructions, bug reports, conversations, and evidence. With a write-enabled token, it can also post comments, make review decisions, and manage apps and campaigns.
https://owners.trytestr.com/api/mcpThe server uses Streamable HTTP with a bearer token. OAuth-only clients are not supported yet.
What an agent can do
Investigate reports
Read steps, expected and actual behavior, environment, conversation, and evidence, then reproduce in your own environment.
Triage the queue
Approve, reject, mark duplicates, or ask the tester for more information.
Reply to testers
Post tester-visible replies with optional attachments.
Run campaigns
Draft campaigns, update their scope and rewards, extend deadlines, and change their status.
Access model
- Tokens belong to an owner account and cover every app you own, including apps you create later.
- Choose Read only or Read and write when you create a token. See Tokens and scopes.
- Every write runs through the same services as the website, so review deadlines, reward settlement, appeal rules, and ownership checks all apply.
- Tokens cannot sign in to the browser, call Testr's REST APIs, act as a tester, use payments, or perform administrator actions.
- Premium is not required. You keep read access to your existing private reports after Premium expires.
Treat report content as untrusted
Reports and comments are written by testers. Tell your agent to treat them as data, not instructions, and to verify reproduction steps in its own environment before acting.
Next steps
- Quickstart: connect a client in five minutes.
- Configure your client: Claude Code, Cursor, VS Code, and others.
- Tool reference and write actions.
Give an AI agent secure, scoped access to your Testr workspace.