Linking with R1-MCP

Probe MCP is a companion to the RUCKUS MCP servers. Linking your Probe MCP account to R1-MCP lets R1-MCP’s Claude reach the on-LAN ground truth a cloud controller can’t see — local inventory, live device CLI, and switch config restore — using your probe.

The link is started from the R1-MCP side

This is the part people get backwards: you begin in R1-MCP, not here. The consent link carries R1-MCP’s signed identity assertion, so it’s minted there.

Open your R1-MCP dashboard and enable the Test Bed Manager feature.
In the Probe (config restore) card, click Connect probe-mcp.
You land on Probe MCP’s link page. If you aren’t signed in, sign in with Google.
Review the two identities shown — your R1-MCP account and your Probe MCP account — and click Connect accounts.

That’s it. The link is one-time and revocable.

Why two identities are shown

The link is gated by two independent facts: a signature proving a trusted sibling (R1-MCP) vouched for that external identity, and your live Probe MCP session proving you own the Probe MCP account. Both must line up, so the consent page shows you both sides before you approve.

What the link grants

Once linked, R1-MCP’s Claude — acting for your linked identity — can call the read and egress probe tools plus serve_tftp / stop_tftp for config restore. It cannot do first-party-only actions like generating scorecards or writing credentials/connections; those stay in your own Probe MCP session.

Moving a link between accounts

If the R1-MCP identity is already linked to a different Probe MCP account, the link is refused unless you explicitly confirm the move (a checkbox that warns the other account loses access). Re-linking the same pair just shows “already connected.”

Revoke a link

From the Probe MCP dashboard, view your links and delete the one you want to revoke. Every link, owner-move, and revoke is recorded in an audit trail.