RoyLead connects to Claude through MCP (Model Context Protocol): from a chat you can ask Claude to manage your account — create domains and link landing pages, read your leads, check campaign ROI, generate creatives with AI and more. Claude acts with your permissions, exactly as you would from the dashboard.
💡 There are two ways to connect, depending on where you use Claude: Claude.ai (browser, desktop app, phone) or Claude Code / Claude Desktop (on your computer). You can use both.
💡 Sensitive actions stay out of the chat for safety: password/email changes, 2FA, billing/payments, deleting a team and removing members are only done from the dashboard.
On Claude.ai you connect with a secure login: no key to paste.
On claude.ai go to Settings → Connectors and choose Add custom connector from the Add menu at the top right.
Settings → Connectors on Claude.ai: from the Add menu choose «Add custom connector» (highlighted by the arrow)
As the MCP server URL, enter:
https://api.roylead.com/api/v1/mcp
The «Add custom connector» dialog: any name you like (e.g. RoyLead) and the MCP server URL in the second field; advanced settings stay empty
The name is up to you (e.g. “RoyLead”); the advanced settings (OAuth Client ID / Secret) stay empty. Confirm to add the connector.
Claude will open RoyLead’s page: sign in with your account (if you haven’t already) and you’ll see a consent screen telling you which application is requesting access and where it will be redirected. Check the address is Claude’s, then click Authorize.
Done: the connector shows as connected and you can start asking Claude to work on RoyLead.
💡 You can revoke access anytime by removing the connector in Claude.ai. Each authorized session is independent.
Here the connection uses a dedicated API Key with the “Claude MCP” scope.
Go to Settings → API and create a new key with the Claude MCP scope.
Give it a recognizable name (e.g. “Claude MCP laptop”) and copy the key (rl_...). You can also reveal it again later with the eye icon.
💡 Use a Claude MCP scoped key, not the WordPress plugin one: they’re deliberately separate, so if one is compromised the other stays safe.
In a terminal, run (replace the key with yours):
claude mcp add roylead --scope user --transport http https://api.roylead.com/api/v1/mcp --header "x-api-key: rl_YOUR_KEY"
The full command in the terminal, with the placeholder key to replace with yours
--scope user makes the connection available in any folder. Then restart Claude Code (MCP servers load at startup) and verify with:
claude mcp list
roylead should appear as connected.
Alternatively, in Claude Desktop’s MCP configuration add:
{
"mcpServers": {
"roylead": {
"type": "http",
"url": "https://api.roylead.com/api/v1/mcp",
"headers": { "x-api-key": "rl_YOUR_KEY" }
}
}
}
Save and restart Claude Desktop.
💡 To remove access later, revoke the key from Settings → API: the connection stops working instantly, without touching your other keys.
Open a new chat with Claude and try asking:
If Claude answers with your data, the connection is live.
What you see | Cause | Fix |
Connector errors on Claude.ai | Wrong address | Use exactly https://api.roylead.com/api/v1/mcp (with api., not app.) |
claude mcp list shows “failed” | Wrong URL or key | Check the URL and that the key has the Claude MCP scope |
“Unexpected content type: text/html” | You used app.roylead.com | The MCP lives on api.roylead.com, not the website |
Claude can’t see the new tools | Session not restarted | Close and reopen Claude Code/Desktop |
An action is refused | Missing permission | Some actions are reserved for team owners/admins, or stay dashboard-only |
If the connection won’t start after checking the URL and key, contact support and mention where you’re connecting from (Claude.ai, Claude Code or Claude Desktop).