What is Probe MCP?

Probe MCP gives Claude eyes on a customer’s live local network — the protocols that only exist on the LAN and never reach a cloud management plane: syslog, SNMP, sFlow, NetFlow, packet capture, and SSH. Cloud-only tools can’t see any of it. A small on-prem probe collects the ground truth, and a Cloudflare engine exposes it to Claude in plain language.

The two halves

• The probe — a single hardened Go container (with a bundled cloudflared tunnel) that you run on one Linux host on the customer LAN. It receives syslog and SNMP traps, polls SNMP, collects sFlow/NetFlow, discovers devices, and can capture packets or open SSH sessions on demand. It stores the raw data locally and dials home over an outbound-only tunnel — no inbound ports.
• The engine — a Cloudflare Worker that ingests the probe’s aggregates, stores them, and serves an MCP server to Claude. You add one URL to Claude as a custom connector and ask your network questions.

The idea: one tool, a whole LAN

Like the sibling r1-mcp server, Probe MCP’s tools/list returns exactly one MCP tool, code_mode. Inside it, Claude writes small JavaScript programs against a probe object that can list your probes, query stored rollups, and reach live into the LAN — SNMP, syslog search, topology, PoE, live packet connections, SSH. See How code mode works.

What you can ask for

• “What’s flooding the syslog on the Charleston probe in the last hour?”
• “Which switch ports are erroring or flapping right now?”
• “Walk the LLDP neighbors and draw me the L2 topology.”
• “Which access points are drawing the most PoE?”
• “Run an assessment on this site and give me a scorecard PDF.”

The workflow prompts in Claude’s + menu package the bigger ones as guided flows.

Standalone, or a RUCKUS companion

Probe MCP stands alone for any network. It is also a companion to the RUCKUS MCP servers: link it to R1-MCP and R1-MCP’s Claude can reach the same on-LAN ground truth — local inventory, ICX/AP CLI, and config restore — that a cloud controller can’t see.

Getting started

1. Sign in and enroll a probe
2. Deploy the probe container on a LAN host
3. Point your devices at it
4. Connect it to Claude

Where your data lives

Raw telemetry stays on the probe by default; only aggregates leave the LAN, and live raw data is fetched on demand over the tunnel. See the Security model.