Connecting to Claude

R1-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 R1-MCP dashboard — https://r1-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. Click Allow.
5. The connector shows as connected, and code_mode appears in Claude’s tools.

What the consent flow is doing

R1-MCP uses OAuth 2.1 with Dynamic Client Registration and PKCE:

1. Claude registers itself as an OAuth client automatically.
2. You are sent to R1-MCP to authorize, which requires your Google session — if you aren’t signed in, you’ll be asked to sign in first.
3. R1-MCP issues Claude an access token bound to your user account. Access tokens last one day; Claude renews them with a 90-day rotating refresh token, so you don’t have to re-authorize.

That token is what makes the single shared MCP URL personal: every request Claude makes carries it, and R1-MCP resolves it to your account and your RUCKUS credentials.

Tokens are stored hashed. R1-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. The prompts appear in the + menu on surfaces that support MCP prompts.

Verifying it’s working

Ask Claude:

Using R1-MCP, list my venues.

If the connector is live but not authorized, Claude will say it can’t authenticate rather than returning an empty list — that distinction is useful when debugging.

When authorization loops or fails

• Redirect loop / “too many redirects” — usually a browser cookie problem during the Google hop. Try in a normal (non-private) window, allow cookies for r1-mcp.lanpulse.com, and re-add the connector.
• Every call fails authentication — 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 RUCKUS side isn’t. Go back to the dashboard and re-run Test on the connection. See Troubleshooting.

Revoking access

Remove the connector in Claude to stop Claude calling it. To revoke access on the server side, click Disconnect all Claude connectors on the R1-MCP dashboard: it revokes every access and refresh token issued to any of your Claude clients. Revoking is immediate — the next request Claude makes fails the bearer check.

Removing the connector does not delete your saved RUCKUS credentials; use the dashboard to delete a connection if that’s what you want. Deleting your last connection also disconnects every Claude connector, the same as the button above.