Getting started
Three steps: sign in, save your RUCKUS One credentials, add the connector to Claude.
1. Sign in
Section titled “1. Sign in”Go to r1-mcp.lanpulse.com and sign in with Google. That Google account is your R1-MCP identity — the same account backs both the web dashboard and the Claude connector.
Tick the Terms of Service checkbox first: sign-in is refused without it. If the terms change later, you’ll be asked to accept them again before you can change connections or re-authorize the Claude connector.
2. Add a RUCKUS One connection
Section titled “2. Add a RUCKUS One connection”In the dashboard’s RUCKUS One connections card, click Add connection and fill in your R1 API credentials:
| Field | Where it comes from |
|---|---|
| Label | Your own name for this tenant, e.g. “Acme Production”. Must be unique among your connections |
| Environment (region) | United States (North America), Europe, or Asia — must match where your tenant lives |
| Client ID | From your RUCKUS One tenant’s API credentials |
| Client secret | Same place. Write-only — once saved it is never shown again |
| Token URL | Filled in for the region you picked (https://api.ruckus.cloud/oauth2/token/{tenantId} for the US). Leave it as is unless RUCKUS told you otherwise |
| Tenant ID | Your R1 tenant identifier. The form marks it optional, but the default token URL needs it — {tenantId} is filled from this field |
When you edit a saved connection, leave the secret blank to keep the stored one. Changing the Client ID or Token URL needs the secret re-entered.
Getting R1 API credentials
Section titled “Getting R1 API credentials”In RUCKUS One, create an API client under your tenant’s administration
settings. You need the client ID, the client secret, and your tenant ID.
R1-MCP uses the OAuth2 client_credentials grant, so no user-interactive
RUCKUS login is involved.
The credential’s permissions in R1 are the ceiling on what Claude can do — R1-MCP cannot exceed them. If you want a read-only experience, issue a read-only API client.
One exception to plan for: opening a live CLI session on an AP needs a read-write API client — RUCKUS One refuses to issue an AP console token to a read-only one. Switch CLI works with either.
Regions
Section titled “Regions”The region selects which RUCKUS One API host your calls go to:
| Region | API host |
|---|---|
| US | api.ruckus.cloud |
| Europe | api.eu.ruckus.cloud |
| Asia | api.asia.ruckus.cloud |
Picking the wrong region is the most common setup failure — the credentials are valid but the tenant isn’t there.
3. Test the connection
Section titled “3. Test the connection”Click Save, then Test on the new connection’s row. This mints a real RUCKUS token with your credentials, so a pass means the whole chain works: client ID, secret, region, and tenant ID.
A pass reads Connection OK — minted an R1 token. A failure reads
Test failed: followed by an error code and detail.
If it fails, see Troubleshooting.
4. Copy your MCP URL and connect Claude
Section titled “4. Copy your MCP URL and connect Claude”Copy the MCP URL from the dashboard, 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
Section titled “5. Try it”Ask Claude something concrete:
List my RUCKUS One venues.
Then something that needs discovery:
How many APs are online at each venue, and which ones are down?
If it works, move on to the prompts — they package the higher-value workflows.
Optional: turn on features
Section titled “Optional: turn on features”The default install covers the R1 REST API and the user guide. Everything else — ICX documentation, webhook analytics, live CLI, test beds — is opt-in per user with no password. See Features.
Multiple tenants
Section titled “Multiple tenants”If you manage more than one RUCKUS One tenant, add each as its own connection and tell Claude which one to use. See Multiple connections.