Getting started

Sign in with Google, save your Cloudpath admin credentials, verify them, and paste one URL into Claude. There is nothing to install.

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).

It must also be publicly routable. Private addresses (10.x, 192.168.x, 172.16–31.x), loopback, link-local, CGNAT ranges, and internal-only names ending .local, .internal, or .localhost are rejected with forbidden_host — CP-MCP runs on Cloudflare, so it can only reach your Cloudpath across the public internet. See Security model.

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. The dashboard confirms with “Saved and verified.” and records a Last verified timestamp.

Caution

Verification only runs when you type a password. If you leave the password field blank to keep the stored one — while changing the FQDN, say — the dashboard saves without checking anything and says “Saved.” rather than “Saved and verified.” Use Test connection to verify what is already stored.

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?

The dashboard controls

Three buttons sit under the credentials form. They do different things, and the difference matters when you are debugging:

Control	What it does
Save & verify	Writes the form to storage. Mints a test JWT only if you typed a password — otherwise it saves without verifying
Test connection	Flushes the cached tokens and re-mints with the stored password, without you retyping it. Reports the new token’s expiry on success, or the error code on failure
Delete	Removes the stored credentials and flushes every cached token. Confirms first, because it stops the connector working

Last verified under the form shows the UTC timestamp of the most recent successful mint, from either Save & verify or Test connection.

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.

If you change the FQDN and leave the password blank, run Test connection afterwards — the save itself will not have checked that the new host accepts the stored credentials.

Next steps

Connecting to Claude Add the custom connector and approve the OAuth consent.

Examples Worked prompts that produce real Cloudpath work end to end.

Security model How your password is encrypted, what is recorded, and how to revoke access.

Troubleshooting What each verification failure means and how to clear it.