FOR DEVELOPERS

Give your agent a way to test like a user.

Add the Percio MCP server once. Then ask from Claude Code or Cursor — Percio runs a persona on its own browser, against a preview URL or localhost, and replies with what to fix.

Add the MCP server

.mcp.json01 · ONCE

{
  "mcpServers": {
    "percio": {
      "command": "npx",
      "args": ["-y", "@percio/mcp"],
      "env": { "PERCIO_API_KEY": "prc_…" }
    }
  }
}

Agent thread02 · EVERY MERGE

Before I merge, have a first-time visitor try the new sign-up on localhost:3000.

percio_start_test → percio_run_status · completed

The persona finished sign-up, but hesitated three times. Worth fixing before merge:

Password rules appear only after the first error
“Continue” sits below the fold
No sign that the confirmation email was sent

Open the report →

Sound familiar

Every check passed. Nobody watched a person try it.

01
E2E tests prove the button works. They say nothing about whether anyone understood what it was for.
02
Usability feedback arrives after the merge, from a support ticket, when the context is already gone.
03
Another dashboard to open is another loop you will skip. The signal has to land where you already work.

Findings your agent can act on

Rated by consequence, with the step and the persona’s words. Your agent reads them in the thread and writes the patch right there.

Findings2 Critical1 High

1
Coupon is accepted with no visual feedback
Critical · Visibility of system status · step 28
“I typed the code, hit apply and nothing happened.” — Marina
Critical3/3
2
Order total does not change after the coupon
Critical · Match between system and the real world · step 31
“I went back to the cart twice to check if the price had dropped.” — Rafael
Critical3/3
3
Declined card error says nothing about what to do next
High · Help users recognize and recover from errors · step 39
“I tried the same card three times without knowing if the problem was me.” — Rafael
High2/3

Evidence, not a red build

Percio does not assert on selectors or fail your pipeline. It shows the step where a person hesitated, and why.

TranscriptMarina

27
Clicked “Apply” next to the coupon field
The button responded, but the page stayed identical: no loading, success or error state appeared.
2m 47s
28
Scrolled to the total and back to the coupon field
Looked for the discount in the summary. The total was unchanged, so she went back and clicked “Apply” a second time.
Critical finding anchored hereCoupon is accepted with no visual feedback
3m 02s

Wired up in two minutes

One MCP entry and a personal API key. Nothing to install on the repository, no GitHub App, no CI plugin.

percio · setup3 STEPS

1Done
Generate a key
Integrations → Agent Integrations → Generate API Key
2Done
Add the entry
Paste it into your MCP config, then restart the client.
{
"mcpServers": {
"percio": {
"command": "npx",
"args": ["-y", "@percio/mcp"],
"env": {
"PERCIO_API_KEY": "$API_KEY"
}
}
}
}
3Done
Check the connection
percio·list_personas
percio responded with the account’s personas

FAQ

Questions developers ask.

Any MCP-capable client — Cursor, Claude Code, Claude Desktop and Windsurf among them. For a pipeline, there is an HTTP API with the same key.

Give your agent a way to test like a user.

Findings your agent can act on

Evidence, not a red build

Wired up in two minutes

Percio for other roles

Ship with confidence,not guesses.

Ship with confidence,
not guesses.