
Your TrueDot workspace,
in every AI tool
Add TrueDot Connect to Claude, Codex, Cursor or any MCP client, sign in once, and let your assistant work in TrueDot with your permissions.
https://connect.truedot.ai/mcp
What your assistant can do
It sees only what your account can see, and every change is checked against your role, exactly as in TrueDot Studio.
Organize research
Browse organizations, research groups and studies, and create new ones.
Build surveys
Questions, sections, matrices, quotas, splits, navigation and visibility rules.
Field and launch
Import documents, clone variants, open or close fielding, and get live links and QR codes.
Analyze results
Track completes, run synthetic responses and export your data.
Search material
Upload research material and search across it.
Shape insights
Create and refine insights and the claims behind them.
Set it up
Your client opens a browser window to sign in the first time it connects. Use the email and password you use for TrueDot Studio.
Add the server from your terminal:
claude mcp add --transport http {{name}} {{url}}Then run /mcp inside Claude Code, pick {{name}} and choose
Authenticate.
For claude.ai and Claude Desktop:
- Open Settings → Connectors and choose Add custom connector.
- Name it
TrueDot Connectand paste the URL:{{url}} - Choose Connect and sign in.
On Team and Enterprise plans, an organization owner adds the connector for the organization first.
Add the server, then sign in:
codex mcp add {{name}} --url {{url}}
codex mcp login {{name}}On older Codex versions, set experimental_use_rmcp_client = true in
~/.codex/config.toml first.
Add this to ~/.cursor/mcp.json, then enable the server under Settings → MCP
and choose Login.
{
"mcpServers": {
"{{name}}": {
"url": "{{url}}"
}
}
}For GitHub Copilot, add this to .vscode/mcp.json (or run MCP: Add Server and
choose HTTP), then start the server and allow the sign-in.
{
"servers": {
"{{name}}": {
"type": "http",
"url": "{{url}}"
}
}
}- Transport: Streamable HTTP. URL:
{{url}} - Auth: OAuth 2.1 with PKCE and dynamic client registration. The client discovers everything from a
401on the URL, or from{{origin}}/.well-known/oauth-protected-resource/mcp. - The client must be able to open a browser for sign-in.