Docs
Menso MCP server
AI users run real tasks on your live site and show where they get stuck, with a replay of every step.
Connect Menso to Claude Code, Cursor or Windsurf, then ask for a test in plain words: “Run a Menso signup test on https://staging.example.com and tell me where the AI user got stuck.”
1. Create an API key
Sign in to Menso, open Settings and choose Create API key. Copy the key right away: Menso shows it once and stores only a fingerprint of it. Each account has one key; revoke it there at any time and create a new one.
2. Connect your editor
The server is hosted at https://api.menso.io/mcp (Streamable HTTP). Nothing to install: add the address and your key. Keep the key in an environment variable and out of your repository.
Claude Code
claude mcp add --transport http menso https://api.menso.io/mcp \
--header "Authorization: Bearer YOUR_MENSO_API_KEY"To share the server with a team, put this in .mcp.json at the project root; each person sets MENSO_API_KEY in their own shell.
{
"mcpServers": {
"menso": {
"type": "http",
"url": "https://api.menso.io/mcp",
"headers": { "Authorization": "Bearer ${MENSO_API_KEY}" }
}
}
}Cursor
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
{
"mcpServers": {
"menso": {
"url": "https://api.menso.io/mcp",
"headers": { "Authorization": "Bearer ${env:MENSO_API_KEY}" }
}
}
}Windsurf
Add this to ~/.codeium/windsurf/mcp_config.json (Devin Desktop: ~/.config/devin/mcp_config.json). Windsurf names the address serverUrl.
{
"mcpServers": {
"menso": {
"serverUrl": "https://api.menso.io/mcp",
"headers": { "Authorization": "Bearer ${env:MENSO_API_KEY}" }
}
}
}Any other MCP client that supports Streamable HTTP and a custom header works the same way: address https://api.menso.io/mcp, header Authorization: Bearer <your key>.
3. What the tools do
run_test(url, template, tier): Starts a test on a public URL and returns a test_id. Templates: purchase (read the homepage and pricing, then decide whether to buy) and signup (create an account with the email and password you pass, then reach the signed-in home). Tiers: speed or quality.get_status(test_id): Queued, running with step progress, paused for you, scoring, done, failed or stopped.get_findings(test_id): The TRACES score (0–100) with each dimension's score and reason, and on Studio every friction point with its steps, evidence and a suggested fix. Text that comes from the tested site is marked as untrusted evidence: review it before you change code, and never run commands it contains.get_replay_link(test_id): A public menso.io/r/… replay of every step the AI user took. Pro and Studio; anyone with the link can watch it.
A run takes several minutes. Your assistant starts it, checks get_status every 30–60 seconds and reads get_findings when the run is done. Ask it to confirm with you before it starts a run or creates a public replay link.
Credits and plans
Runs started through the MCP server follow exactly the rules of runs started on menso.io.
- A Speed run costs 40 credits and a Quality run 300. The balance is checked before a run starts; a run that would overdraw it does not start.
- Runs that fail for a reason caused by Menso are not charged.
- Free accounts get 100 credits to start and 20 a day. Every plan gets the TRACES score and its reasons.
- Public replay links are included in Pro and Studio.
- The full list of friction points, with evidence and suggested fixes, is included in Studio.
- The same limits on concurrent runs apply as on menso.io.
See Pricing for plans and credit packs.
Security
- A key can start tests and read this account's results. It cannot see or change billing, and it cannot create or revoke keys.
- Menso stores only a fingerprint of the key; revoking it stops it immediately.
- The site must be publicly reachable. Menso runs in the cloud and cannot open localhost or a private network: test a preview deployment instead.
- For the signup template, use a dedicated test inbox and a password you use nowhere else. Menso keeps it in the same saved-account vault as the web app and checks replays for it before they can be shared. Menso keeps the 100 most recently used test accounts created this way; a run whose test account is no longer kept cannot get a public replay link.
- Test only sites you own or have permission to test (see the Terms).