Recommended setup — npx + API key
You don’t need to install anything globally. Create or edit .cursor/mcp.json in your project:
YOUR_PERCIO_API_KEY with the key from your Percio dashboard (Integrations → Agent integrations).
Restart Cursor or reload MCP servers. The Percio tools should now be visible.
Alternative — use percio login credentials
If you’ve already run percio login on your machine, you can drop the --api-key:
~/.config/percio/credentials.json automatically.
Project-scoped vs. user-scoped config
Cursor supports both:- Project-scoped —
.cursor/mcp.jsonin the root of a project. Only applies when Cursor opens that project. Good for per-project keys. - User-scoped —
~/.cursor/mcp.json. Applies across all projects. Good when the same key is used everywhere.
Reloading after a config change
Changes tomcp.json only take effect after Cursor reloads its MCP servers. Either:
- Restart Cursor, or
- Open the MCP settings panel in Cursor and reload servers.
Verifying it’s wired up
In Cursor, the MCP tools panel should list:list_personaschat_scenariochat_personacreate_personarun_usability_test
First prompt to try
Once the tools show up, try asking Cursor:
“Can you run a usability test on my sign-up flow at http://localhost:3000/signup? I want to test it as a first-time visitor.”
Cursor will:
- Call
list_personasto see what’s available. - Ask you to pick one or offer to create a new persona via
chat_persona+create_persona. - Walk through
chat_scenariowith you to build a scenario — it will relay each question verbatim and wait for your answer. - Confirm the scenario with you.
- Call
run_usability_testwith the chosen persona and scenario.
Using with other MCP clients
Thepercio-mcp command works with any MCP-capable client. Claude Desktop and other clients use the same configuration pattern — point the client at the npx percio-mcp command and pass your API key via --api-key or environment.