Getting started

Three steps: sign in, save your Cloudpath credentials, add the connector to Claude.

1. Sign in

Go to cp-mcp.lanpulse.com and sign in with Google. That Google account is your CP-MCP identity — the same account backs both the web dashboard and the Claude connector.

2. Save your Cloudpath credentials

In the dashboard, enter the admin credentials for your Cloudpath deployment:

Field	What it is
FQDN	The bare hostname of your Cloudpath server, e.g. jeff245.cloudpath.net — no https://, no path
Username	Your Cloudpath admin username
Password	The password for that admin account. It is write-only — once saved it is never shown again
Label	Optional. Your own name for this deployment

Caution

The FQDN must be a bare hostname — no scheme and no path. Entering https://jeff245.cloudpath.net or a URL with a path is rejected with fqdn must be a bare hostname (no scheme, no path).

The credentials you save are the ceiling on what Claude can do. CP-MCP does not layer its own role model on top of Cloudpath — access is governed entirely by the admin account you save here. Use Cloudpath’s role-based access controls to scope that account. See Security model.

3. Save & verify

Click Save & verify. CP-MCP logs in to your Cloudpath by minting a real JWT against the Core surface, so a pass means the whole chain works: FQDN, username, and password.

If it fails, see Troubleshooting.

Note

Your Cloudpath server must present a publicly trusted TLS certificate. Cloudflare Workers reject self-signed certificates on outbound HTTPS. Cloud-hosted Cloudpath at *.cloudpath.net already does; on-premises installs need a certificate from a public CA. See Security model.

4. Copy your MCP URL and connect Claude

Copy the MCP URL from the dashboard — https://cp-mcp.lanpulse.com/mcp/ — then follow Connecting to Claude.

The URL is the same for every user. What identifies you is the OAuth token Claude obtains when it connects, which is bound to your account.

5. Try it

Ask Claude something concrete:

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

Then something that needs discovery:

How many registration lists are configured, and how many entries are in each?

Changing deployments or rotating the password

The MCP URL is static and tied to your account, not to a specific Cloudpath deployment. To point at a different Cloudpath, or to rotate the password, update the fields in the dashboard and save — no change is needed in Claude. Saving new credentials flushes the cached Cloudpath tokens, so the next call mints a fresh one. See Security model.