Developers · MCP server
mocktomer ships a remote MCP server. Tell Claude, ChatGPT, or Cursor to send shoppers through your site — personas browse it live, AI visibility runs score how the assistants see it, and the full report comes back to the conversation. Works in chats, agents, and CI pipelines.
Two-minute setup
Claude.ai · connectors (OAuth)
Settings → Connectors → Add custom connector URL: https://mocktomer.ai/mcp → Sign in with your mocktomer account when prompted. OAuth — no API key to paste.
Claude Code
claude mcp add --transport http mocktomer \ https://mocktomer.ai/mcp # then /mcp → authenticate (OAuth sign-in) # or pin an API key instead: claude mcp add --transport http mocktomer \ https://mocktomer.ai/mcp \ --header "Authorization: Bearer mk_live_YOUR_KEY"
Cursor · any JSON config
{
"mcpServers": {
"mocktomer": {
"url": "https://mocktomer.ai/mcp",
"headers": { "Authorization": "Bearer mk_live_YOUR_KEY" }
}
}
}ChatGPT — developer mode
Settings → Connectors → Advanced → Developer mode → Add connector URL: https://mocktomer.ai/mcp Auth: Bearer mk_live_YOUR_KEY
Then: “Test mystore.com with 5 shoppers and tell me why people bail at checkout.” The assistant adds the site, launches, polls, and reads the report back — in one conversation.
The tool surface
list_sitessites in the workspace, with status + persona countsadd_sitecrawl a new site, understand the business, generate the persona castlaunch_testsend shopper personas + AI visibility runs in; returns run_id instantly (~10 min runs)get_run_statuslive per-shopper progress + AI pass stateget_reporthealth score, summary, every finding with fixes and real quotesget_ai_readiness0–100 score + which competitors ChatGPT/Claude/Gemini recommend insteadtriage_findingmark findings fixed / ignored / out of scopeshare_replaymint (or revoke) the public replay link for a runrerun_verifyfocused follow-up run that verifies your fixesSecurity model
FAQ
Everything in the core loop: list and add sites, send human personas and AI shoppers in, poll run status, read the full experience report (findings, fixes, shopper quotes), read the AI Readiness Score with the competitors assistants recommend instead, mint public replay links, triage findings, and launch verification re-runs.
Two ways in, both hashed at rest and never admin-powered. Claude connectors use OAuth: you sign in and approve access, and the connector holds short-lived tokens you revoke by disconnecting it. Everything else uses scoped API keys minted in Settings: shown once, optionally auto-expiring, instantly revocable, with a per-key daily run cap as a circuit breaker against leaked keys and runaway agent loops. Every launch spends the account's normal credits with the same guardrails as the dashboard.
Any MCP client that supports remote servers over Streamable HTTP: Claude.ai and Claude Code connect with OAuth (paste the URL, sign in when prompted), while ChatGPT developer mode, Cursor, and the Claude Messages-API MCP connector connect with a bearer API key. Same nine tools either way.
The MCP server is free on every plan — runs launched through it spend your normal persona and AI-visibility credits, exactly like runs launched from the dashboard. Free accounts get 10 shopper personas monthly.