# R1-MCP

> MCP server (Claude connector) for RUCKUS One. Google sign-in; calls any of the 1500+ R1 API endpoints, plus floorplan maps, venue and config copy, backups, live device CLI, webhook analytics and MOP workflows.

All of these pages as one Markdown file: https://docs.neuralconfig.com/r1-mcp/llms-full.txt
Support: https://support.neuralconfig.com/r1-mcp

## Pages

- [What is R1-MCP?](https://docs.neuralconfig.com/r1-mcp/): R1-MCP lets you ask Claude about your RUCKUS One network in plain language — inventory, RF, clients, switch config, config copy and backup, floor maps — against the live API of your own tenant, through one connector URL.
- [Getting started](https://docs.neuralconfig.com/r1-mcp/setup/getting-started/): Sign in to R1-MCP with Google, add your RUCKUS One API credentials, test the connection, and get your MCP URL.
- [Connecting to Claude](https://docs.neuralconfig.com/r1-mcp/setup/connecting-claude/): Add R1-MCP as a custom connector in Claude — the MCP URL, the OAuth consent flow, and what to do when the connector won't authorize.
- [Multiple RUCKUS One connections](https://docs.neuralconfig.com/r1-mcp/setup/connections/): Managing several RUCKUS One tenants from one R1-MCP account — adding connections, choosing one per call, defaults, and how tenant isolation is enforced.
- [How code mode works](https://docs.neuralconfig.com/r1-mcp/concepts/how-code-mode-works/): Why R1-MCP exposes one MCP tool instead of 1500 — the discovery-then-call workflow, the sandboxed isolate, error handling, retries, and the run budget.
- [Security model](https://docs.neuralconfig.com/r1-mcp/concepts/security/): How R1-MCP handles your credentials — encryption at rest, server-side token minting, what Claude can and cannot see, and how access is authorized and revoked.
- [Core tools reference](https://docs.neuralconfig.com/r1-mcp/reference/core-tools/): The tools every R1-MCP user gets with no features enabled — find any RUCKUS One API operation, call it on your tenant, search the RUCKUS One guides, pick a tenant, and run common multi-step jobs like RF analysis and topology diagrams.
- [Workflow prompts](https://docs.neuralconfig.com/r1-mcp/reference/prompts/): The 18 guided workflow prompts R1-MCP puts in Claude's "+" menu — RF health checks, client deep-dives, as-built packets, topology diagrams, POC test plans, and more.
- [Features and feature flags](https://docs.neuralconfig.com/r1-mcp/reference/features/): The optional R1-MCP features you can enable per account — ICX, webhooks, Edge, write guard, live CLI, test bed, copy, floorplan — the password-gated Early Access features, and the admin-granted AI chat.
- [Bundled reference docs](https://docs.neuralconfig.com/r1-mcp/reference/reference-docs/): The get_reference tool and the 20 curated reference documents R1-MCP ships — ICX workflows and STIG validation, GraphQL schemas, MOP authoring, venue copy, probe verification, Data Studio, floorplan mapping, and VLAN probe.
- [Limits and quotas](https://docs.neuralconfig.com/r1-mcp/reference/limits/): Every R1-MCP timeout, per-user cap, size limit, and retention window in one place — the run budget, stored artifacts, webhook event retention, and what happens when you hit each one.
- [ICX switches and FastIron docs](https://docs.neuralconfig.com/r1-mcp/features/icx/): The R1-MCP ICX feature — searching the FastIron command reference and configuration guides by firmware train, and the end-to-end switch configuration workflow.
- [Live CLI and MOPs](https://docs.neuralconfig.com/r1-mcp/features/live-cli/): The R1-MCP live_cli feature — running real commands on ICX switches and APs through device_cli, and authoring, recording, replaying, and exporting MOPs and test plans.
- [Webhooks and analytics](https://docs.neuralconfig.com/r1-mcp/features/webhooks-and-analytics/): The R1-MCP webhooks feature — the inbound event receiver, plus incident, client, anomaly, audit, and roaming analytics built on the events it collects.
- [Write Guard](https://docs.neuralconfig.com/r1-mcp/features/write-guard/): Confirm-before-write for R1-MCP — how the preview and confirmation token work, what counts as a write, and why you should turn it on for production tenants.
- [Test beds](https://docs.neuralconfig.com/r1-mcp/features/testbed/): The R1-MCP testbed feature — capture, plan, and apply lab hardware swaps between saved configuration sets, with export, import, and config restore.
- [Venue config copy](https://docs.neuralconfig.com/r1-mcp/features/venue-copy/): The R1-MCP copy feature — snapshot a venue's configuration, plan a copy into another venue or another tenant, review it, run it, verify it, and undo it.
- [What a venue copy carries](https://docs.neuralconfig.com/r1-mcp/features/venue-copy-support/): The per-domain support matrix for R1-MCP venue copy — which configuration carries same-tenant, cross-tenant, and into a template, and what is never copied.
- [Copying one object](https://docs.neuralconfig.com/r1-mcp/features/element-copy/): Element copy in R1-MCP — extract a single WLAN, switch profile, or AP ethernet-port profile with its whole dependency closure and recreate it in another RUCKUS One tenant.
- [Venue backups](https://docs.neuralconfig.com/r1-mcp/features/backups/): Capture a RUCKUS One venue's configuration and keep it — encrypted, retained indefinitely, and restorable into the same venue, a new one, or another tenant.
- [GraphQL API support](https://docs.neuralconfig.com/r1-mcp/features/graphql/): The R1-MCP graphql Early Access feature — call_r1_gql against the four RUCKUS AI GraphQL services, why introspection is unavailable, and how errors surface.
- [Probe — on-LAN ground truth](https://docs.neuralconfig.com/r1-mcp/features/probe/): The R1-MCP probe Early Access feature — linking your Probe MCP account, the read-only probe tools available, and reconciling the RUCKUS One inventory against what's actually on the wire.
- [Data Studio dashboards](https://docs.neuralconfig.com/r1-mcp/features/data-studio/): The R1-MCP datastudio Early Access feature — the 16 ds_* tools that discover datasets, validate queries, and build and publish charts and dashboards in RUCKUS One Data Studio headlessly.
- [Live Console](https://docs.neuralconfig.com/r1-mcp/features/live-console/): The R1-MCP console Early Access feature — a browser page that streams a watched client's events and plots RSSI, SNR, and Tx while you troubleshoot in Claude.
- [Floorplans and floor maps](https://docs.neuralconfig.com/r1-mcp/features/floorplans/): How R1-MCP reads a venue's floorplans, places every AP and switch in real metres, and renders a floor as an image with findings — what the floorplan feature can and cannot tell you, its tools, the Floor Map page, and its limits.
- [Floor map layers](https://docs.neuralconfig.com/r1-mcp/features/floorplan-layers/): Every layer floorplan_map can draw over a venue floor — clients, bands, roaming, entry points, co-channel, predicted coverage, AP failure impact, demand and the LBS layers — what each one can and cannot state, what it needs, and which layer wins when two compete.
- [The roam matrix](https://docs.neuralconfig.com/r1-mcp/features/roam-matrix/): What the R1-MCP roam matrix is, where its data comes from, how to read a pair (signal change, fast-roam share, placement concern), how it is drawn on a floor, and what it cannot tell you.
- [Location-based services (LBS)](https://docs.neuralconfig.com/r1-mcp/features/lbs/): What LBS (location-based services) adds to R1-MCP floor maps — measured client positions, Locate, airtime, devices heard — what it needs, how a source is set up, its accuracy and what it keeps.
- [VLAN probe](https://docs.neuralconfig.com/r1-mcp/features/vlan-probe/): The R1-MCP vlan_probe Early Access feature — testing whether a VLAN is reachable over wireless at a venue with no WLAN on it, what a run puts on the air, how it is torn down, what the verdicts mean, and how to find anything left behind.
- [Examples](https://docs.neuralconfig.com/r1-mcp/examples/): Worked examples of asking Claude to do real RUCKUS One work through R1-MCP — inventory, RF analysis, client troubleshooting, diagrams, and switch configuration.
- [Troubleshooting](https://docs.neuralconfig.com/r1-mcp/troubleshooting/): Fixes for common R1-MCP problems — failed connection tests, connector authorization loops, missing tools or prompts, 401s and 429s, and wrong FastIron syntax.