Workflow prompts
R1-MCP serves a set of curated MCP prompts — guided workflows that appear in Claude’s + menu. Each one is a well-tested sequence for a job people actually do, so you don’t have to describe the whole procedure yourself.
You only see prompts for features you have enabled.
Always available
Section titled “Always available”| Prompt | What it does |
|---|---|
| Explore the RUCKUS One API | Orientation — find your way around the API taxonomy and try calls |
| RF health check (venue) | RF assessment for a venue over a time window |
| Venue documentation packet (as-built) | Assembles an as-built document for a site; you choose which sections |
| Topology diagrams (L1 / L2 / L3) | Network diagrams at the layers you pick |
| Client deep-dive troubleshooting report | Everything about one client MAC — connections, roams, incidents |
| Configuration & state audit | Audits configuration and current state across a scope you set |
Webhooks feature
Section titled “Webhooks feature”Requires the webhooks feature.
| Prompt | What it does |
|---|---|
| Network health check (incidents) | Health assessment driven by incident data |
| Hunt infrastructure anomalies | Looks for anomalies across infrastructure |
| Admin / change audit trail | Who changed what, and when |
| Live reproduce-and-catch (watch & capture) | Arms watches on a client or AP, then captures what happens while you reproduce a problem |
ICX feature
Section titled “ICX feature”| Prompt | What it does |
|---|---|
| ICX BGP-EVPN fabric build / validate | Builds or validates a BGP-EVPN fabric on ICX switches |
Live CLI feature
Section titled “Live CLI feature”| Prompt | What it does |
|---|---|
| POC / QA test plan (author → run → report) | Writes a test plan against an objective, runs it, and reports |
| Deep-dive an ICX switch / fleet (live CLI) | Investigates a switch or fleet against a symptom, on the live console |
Test Bed feature
Section titled “Test Bed feature”| Prompt | What it does |
|---|---|
| Swap lab hardware to a saved test bed | Moves lab hardware between saved configuration sets |
Using a prompt
Section titled “Using a prompt”Pick it from the + menu, fill in the arguments it asks for (venue, time window, client MAC, scope, and so on), and send. The prompt seeds the conversation with the workflow; from there it’s a normal conversation and you can redirect it at any point.
You are never required to use prompts — everything they do can be asked for in your own words. They exist because the good version of “give me an as-built packet” is a page of instructions nobody wants to retype.
If a prompt isn’t showing
Section titled “If a prompt isn’t showing”- Check that the feature it belongs to is enabled on your account.
- Reconnect the connector — prompt lists are fetched when the connector refreshes, so a newly enabled feature may need a reconnect to appear.
- Confirm your Claude surface supports MCP prompts; not every client shows the + menu.