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.

What it does for you

R1-MCP turns day-to-day RUCKUS One work into a conversation:

• Inventory and health — venues, APs, switches and clients, what is online, what is down, and why.
• RF and clients — airtime, channel plans, co-channel candidates, a single client’s disconnects, and roaming between APs.
• Switch configuration — FastIron syntax checked against the command reference for your firmware train, applied through RUCKUS One, and live CLI on switches and APs when you need the console.
• Copy and backup — snapshot a venue’s configuration, copy it into another venue or tenant, and keep encrypted backups you can restore.
• Floor maps — your APs placed on the venue floorplan with coverage, roaming and co-channel findings drawn on it.
• Documentation — as-built packets, topology diagrams, and answers drawn from the RUCKUS One user guide.

Your R1 API credentials set the limit on all of it: R1-MCP can do exactly what your RUCKUS One API client is allowed to do.

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 direct API calls (call_r1 and call_r1_gql)
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
Copy	Snapshot a venue’s config and copy it into another venue or another tenant
Floorplan	Venue floor maps with APs placed, plus coverage, client, roaming and co-channel layers, rendered as an image

Plus password-gated Early Access features: GraphQL against the RUCKUS analytics services, on-LAN ground truth via Probe MCP, Data Studio chart building, the Live Console, and VLAN probe — wireless VLAN reachability tested through a temporary SSID, started from the r1-mcp companion extension.

How it reaches the whole 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.

Getting started

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

Explore the docs

Set up

Getting started Sign in with Google, add your RUCKUS One API credentials, test the connection, and get your MCP URL.

Connecting to Claude Add R1-MCP as a custom connector — the MCP URL, the OAuth consent, and what to do when it doesn't appear.

Multiple connections Manage several RUCKUS One tenants from one account, and tell Claude which one to work against.

How it works

How code mode works Why R1-MCP exposes one MCP tool instead of 1500, and how Claude discovers an endpoint before calling it.

Security model Where your credentials live, how tokens are minted server-side, and what Claude can and cannot see.

Reference

Core tools The tools every account gets — API discovery, calling any RUCKUS One endpoint, and documentation search.

Workflow prompts The 18 guided workflows in Claude's + menu, from RF health to as-built documentation.

Features and feature flags Every optional feature, what it adds, and how to turn it on for your account.

Bundled reference docs The 20 curated documents R1-MCP ships, and the get_reference tool that searches them.

Limits and quotas The run budget, per-user caps on stored artifacts, event retention windows, and what each limit does when you hit it.

Feature guides

ICX switches Search the FastIron command reference by firmware train, and run the end-to-end switch configuration workflow.

Live CLI and MOPs Run real commands on switches and APs, then author, record, and replay MOPs and test plans.

Webhooks and analytics Receive RUCKUS One events, and query incident, client, anomaly, and roaming analytics built from them.

Write Guard Confirm-before-write on direct API calls — what counts as a write, what it does not cover, and why production tenants want it.

Test beds Capture, plan, and apply lab hardware swaps between saved configuration sets.

Venue config copy Snapshot a venue's configuration and copy it into another venue or tenant — plan, run, verify, undo.

What a venue copy carries The per-domain support matrix: which configuration a copy moves, and which it leaves behind.

Copying one object Move a single WLAN, switch profile, or ethernet-port profile — with everything it depends on — to another tenant.

Venue backups Keep a venue's configuration indefinitely and encrypted, then restore it in place, as a new venue, or into another tenant.

Floorplans and floor maps Read a venue's floorplans with every AP and switch placed, and render a floor as an image with findings attached.

Floor map layers The layers you can draw on a floor — clients, roaming, co-channel, predicted coverage, AP failure impact — and what each one can and cannot tell you.

GraphQL API support Early Access. Query the four RUCKUS AI GraphQL services, and why introspection is unavailable.

Probe — on-LAN ground truth Early Access. Reconcile the RUCKUS One inventory against what a probe actually sees on the wire.

Data Studio dashboards Early Access. The 16 ds_* tools for building charts and dashboards from your network data.

Live Console Early Access. A browser page streaming a watched client's events, plotting RSSI, SNR, and Tx live.

VLAN probe Early Access. Test whether each VLAN is reachable over wireless by putting up a temporary SSID and running Service Guard, then tearing it all down.

More

Examples Worked examples of asking Claude to do real RUCKUS One work end to end.

Troubleshooting Failed connection tests, connector authorization loops, missing tools, 401s and 429s.

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.