Connecting to Claude

CP-MCP is a remote MCP server. There is nothing to install locally — you add one URL as a custom connector and authorize it.

Add the connector

1. Copy your MCP URL from the CP-MCP dashboard — https://cp-mcp.lanpulse.com/mcp/.
2. In Claude, go to Settings → Connectors → Add custom connector.
3. Paste the URL and add it.
4. Claude opens a consent page. Approve it.
5. The connector shows as connected, and code_mode appears in Claude’s tools.

Note

code_mode is the only tool the connector exposes, and CP-MCP publishes no MCP prompts. Everything you do runs through that one tool — see How code mode works.

What the consent flow is doing

CP-MCP uses OAuth 2.1 with Dynamic Client Registration (RFC 7591) and PKCE:

1. Claude registers itself as an OAuth client automatically.
2. You are sent to CP-MCP to authorize, which requires your Google session — if you aren’t signed in, you’ll be asked to sign in first.
3. CP-MCP issues Claude an access token bound to your user account.

That token is what makes the single shared MCP URL personal: every request Claude makes carries it, and CP-MCP resolves it to your account and your saved Cloudpath credentials. Tokens are stored hashed — CP-MCP never holds a raw copy of a token it issued.

Where it works

Any Claude surface that supports custom connectors — Claude Desktop, Claude on the web, and Claude Code.

Verifying it’s working

Ask Claude:

Using CP-MCP, list the authentication servers on my Cloudpath.

If the connector is live but your Cloudpath credentials are missing or wrong, Claude gets a structured error telling it to save credentials in the dashboard, rather than a silent empty result — that distinction is useful when debugging.

When authorization loops or fails

• Redirect loop / “too many redirects” — usually a browser cookie problem during the Google sign-in hop. Try a normal (non-private) window, allow cookies for cp-mcp.lanpulse.com, and re-add the connector.
• “Not authenticated” on every call — the token was revoked, or the connector was added before you finished signing in. Remove the connector and add it again.
• Connected, but every call errors about credentials — the MCP side is fine and the Cloudpath side isn’t. Go back to the dashboard and click Test connection, which re-mints against the stored password and names the exact failure. See Troubleshooting.

Revoking access

Remove the connector in Claude to stop it making requests. To cut off Cloudpath access entirely, delete your credentials in the dashboard — that takes effect immediately, with no window in which a cached token still works. See Security model. Removing the connector does not delete your saved Cloudpath credentials.

Next steps

Examples Prompts that produce real Cloudpath work once the connector is live.

How code mode works Why there is only one tool, and what Claude does with it.

Troubleshooting Authorization loops, credential errors, and every error code.