What is R1-MCP?

R1-MCP is a hosted MCP server that connects Claude to your RUCKUS One tenant. You sign in with Google, save your R1 API credentials, and add one URL to Claude as a custom connector. From then on you can ask Claude about your network in plain language, and it works against the live R1 API on your behalf.

It covers the whole API — all 1500+ RUCKUS One endpoints — plus the RUCKUS One user guide, FastIron documentation for ICX switches, and a set of guided workflow prompts.

The idea: one tool, an entire API

Most MCP servers expose one MCP tool per API operation. With 1500+ endpoints that would be unusable — no model can pick sensibly from a list that long, and the tool definitions alone would swamp the context window.

R1-MCP instead exposes exactly one MCP tool, code_mode. Inside it, Claude writes small TypeScript programs against an r1 object that can discover endpoints and call them. So instead of choosing from 1500 tools, Claude searches the API index, reads the endpoint’s schema, and calls it — the same way you would with the docs open.

That code runs in a sandboxed V8 isolate on Cloudflare, with your credentials applied server-side. Read How code mode works for the mechanics.

What you can ask for

Some things people actually use it for:

• “What’s the RF health at the Charleston venue over the last 24 hours?”
• “Find the client with MAC aa:bb:… and tell me why it keeps disconnecting.”
• “Draw me an L2 topology diagram of this venue.”
• “Build an as-built documentation packet for this site.”
• “Which APs have the worst airtime utilization this week?”
• “Generate the FastIron config to add VLAN 200 tagged on ports 1/1/1-1/1/8.”

The MCP prompts in Claude’s + menu package the bigger ones as guided workflows.

Beyond the REST API

Optional features extend the surface well past R1’s REST endpoints:

| Feature | What it adds | |---|---| | ICX | Full-text search over FastIron command reference and config guides, plus an end-to-end switch config workflow | | Webhooks | An inbound webhook receiver plus incident, client, anomaly, and roaming analytics | | Edge | RUCKUS Edge documentation search | | Write Guard | Confirm-before-write on any mutating call | | Live CLI | A held console session to devices, and MOP author / record / replay | | Test Bed | Capture, plan, and apply lab hardware swaps between saved config sets |

Plus password-gated Early Access features: GraphQL against the RUCKUS analytics services, on-LAN ground truth via Probe MCP, and Data Studio chart building.

Getting started

1. Sign in and add your R1 credentials
2. Connect it to Claude
3. Try one of the prompts or an example

How your credentials are handled

Your R1 client secret is encrypted at rest, decrypted only when minting a RUCKUS token, and never sent to Claude or included in any model context. See Security model.