Connect MCP clients
Connect Claude Code, Claude Desktop, or ChatGPT to your live Recense session in four steps: load a dataset, generate an API key, add the relay endpoint, and test with a read-only prompt. The assistant works with your live session — not a separate copy.
How it works #
Your MCP client connects to Recense, which routes tool calls to the browser session you have open. The client works with the same session you see — not a separate copy.
Setup (all clients) #
The setup flow is the same for all MCP clients:
-
Open Recense in the browser, sign in, and load a dataset.
The MCP client needs a live session to connect to.
-
Generate an API key in Account → API Access.
The relay uses your Recense API key for authentication.
-
Add the Recense MCP server in your client using the relay endpoint.
Use the endpoint URL below and send your API key as a Bearer token.
-
Test with a read-only request.
Try "describe the dataset" or "list variables" to confirm the connection works.
https://mcp.recense.ai/mcp Per-client notes #
Claude Code — add a new MCP server pointing to the endpoint above. Claude Code handles connection setup. Ideal for users who want Recense tools alongside their coding workflow.
Claude Desktop — add the endpoint in Claude Desktop's MCP server settings. Authentication is discovered automatically — no extra configuration needed.
ChatGPT Desktop — same endpoint as above. Start with read-only prompts (dataset description, variable listing) before moving to analysis actions.
Custom clients #
Supported today:
- Live session relay — your client controls a signed-in browser session with full app access.
- Headless CLI — direct access against a .sav file without a browser. Analysis engine only (no workspace UI).
recense-cli mcp --file /path/to/data.sav --name "My Survey" Available tools #
All MCP clients can:
- Inspect dataset structure, variables, and metadata.
- Build and modify tables on the canvas.
- Apply filters, weights, and measures.
- Read analysis results.
Troubleshooting #
- Client can't connect: verify the endpoint URL ends in /mcp, not just the site root.
- Tool calls fail: check the Recense browser tab is still open and signed in.
- Sign-in keeps looping: confirm you're signing in with the same account you expect the client to control.
- Tier issue: verify your Recense plan includes MCP access.