DoubleScale generates ready-to-paste connection snippets for popular MCP clients. All snippets point at your site’s MCP endpoint and include the Authorization header your client needs.
General rules
- One key per client — Create separate API keys for Claude Code, Cursor, etc. Revoke one without breaking the others.
- Treat snippets like passwords — They contain your API key. Do not commit them to Git, paste them in public chats, or share screenshots.
- Use a reachable URL — A
localhostendpoint only works on the same machine. Remote clients need your public site URL. - Restart clients after changes — Many MCP clients cache the tool list at connect time. Fully quit and reopen the app after enabling MCP or changing keys.
Claude Code
Run the snippet in your terminal:
claude mcp add
--transport http
doublescale https://yoursite.com/wp-json/doublescale/mcp
--header "Authorization: Bearer YOUR_API_KEY"
Claude Code connects directly over HTTP — no Node helper required.
Cursor
Add to Cursor’s MCP config (Settings → Tools & MCP):
{
"mcpServers": {
"doublescale": {
"url": "https://yoursite.com/wp-json/doublescale/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Claude Desktop
Add to claude_desktop_config.json:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%Claudeclaude_desktop_config.json
Claude Desktop uses the mcp-remote Node helper. You need Node.js installed (node -v should work in a terminal).
On Windows, DoubleScale’s snippet routes through cmd /c and passes the auth header via an environment variable — both are required because Windows splits paths and headers at spaces.
OpenAI Codex
Add to ~/.codex/config.toml. Codex also uses the mcp-remote helper and requires Node.js.
Other MCP clients
Any client that supports HTTP transport with custom headers can connect:
- Endpoint:
https://yoursite.com/wp-json/doublescale/mcp - Transport: HTTP (JSON-RPC 2.0)
- Header:
Authorization: Bearer YOUR_API_KEY(or Basic for Application Passwords)
Emailing setup instructions
After creating a key, you can email setup steps to the key owner from the MCP settings page. By default the email contains configuration instructions only — not the key itself. Check “Include the key itself in the email” only if you accept the security trade-off (keys in inboxes persist in backups and mail providers).
Quill Forms integration
DoubleScale and Quill Forms share the same integration path: form submissions flow into DoubleScale contacts and can trigger automations. MCP does not replace the Quill Forms connector — it gives AI agents access to CRM data after submissions are already in DoubleScale. Install DoubleScale, connect Quill Forms under DoubleScale → Integrations, then use MCP to query or act on the contacts those forms create.


