# Probe MCP

> On-premises network probe (single-file Go container + cloudflared tunnel) with a Cloudflare Worker engine and MCP server exposing LAN telemetry to Claude.

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

## Pages

- [What is Probe MCP?](https://docs.neuralconfig.com/probe-mcp/): Probe MCP puts a small on-prem probe on a customer LAN and exposes what it sees — syslog, SNMP, sFlow, packet capture, SSH — to Claude through one MCP connector.
- [Getting started](https://docs.neuralconfig.com/probe-mcp/setup/getting-started/): The four steps to a working Probe MCP setup — sign in with Google, enroll a probe, deploy it on a LAN host and point devices at it, then connect Claude.
- [Deploying the probe](https://docs.neuralconfig.com/probe-mcp/setup/deploying-the-probe/): Run the Probe MCP container on a LAN host — the host requirements, the docker run one-liner with host networking, the single-use activation code, the data volume, and verifying it's Online.
- [Pointing your network at the probe](https://docs.neuralconfig.com/probe-mcp/setup/sending-telemetry/): Configure your switches, APs, and firewalls to send telemetry to the probe — syslog on 514, SNMP traps on 162, sFlow on 6343, NetFlow on 2055 — plus SNMP polling and which collectors are on by default.
- [Connecting to Claude](https://docs.neuralconfig.com/probe-mcp/setup/connecting-claude/): Add Probe MCP as a custom connector in Claude — the MCP URL, the OAuth 2.1 consent flow with Google sign-in, where it works, and how to verify and revoke access.
- [Configuring the probe](https://docs.neuralconfig.com/probe-mcp/setup/configuring-the-probe/): The probe's YAML config file — the collector sections and their real defaults, how to enable optional services like sFlow, packet capture, SSH and TFTP, the environment-variable overrides, and the CLI flags.
- [API connections and the vault](https://docs.neuralconfig.com/probe-mcp/setup/connections/): Register upstream APIs that Claude can call with a server-injected secret — the cloud, probe-vault, and fallback storage modes, the post-quantum probe vault, and break-glass access when the probe is offline.
- [How code mode works](https://docs.neuralconfig.com/probe-mcp/concepts/how-code-mode-works/): Probe MCP exposes one MCP tool, code_mode, that runs small JavaScript programs against a probe object — and the key split between stored data (works offline) and on-demand data (needs the probe online).
- [Security model](https://docs.neuralconfig.com/probe-mcp/concepts/security/): How Probe MCP handles an AI agent on your LAN — data residency, the outbound-only tunnel with no inbound ports, HMAC-signed telemetry, hashed OAuth tokens, an encrypted post-quantum vault, and the privileges the probe container needs.
- [Probe tools reference](https://docs.neuralconfig.com/probe-mcp/reference/probe-tools-reference/): The probe.* functions Claude can call inside code_mode — reference lookups, stored rollups, on-demand LAN queries, API connections and the vault, device SSH CLI, and the assessment scorecard.
- [Workflow prompts](https://docs.neuralconfig.com/probe-mcp/reference/prompts/): The two guided MCP prompts Probe MCP puts in Claude's "+" menu — an assessment scorecard that renders a co-branded PDF, and a read-only tour of what your probe can see.
- [Limits and budgets](https://docs.neuralconfig.com/probe-mcp/reference/limits/): Every limit that can end a Probe MCP request — the code_mode wall-clock budget, the tunnel round-trip timeout, per-function row and size caps, the services that ship disabled, how long the probe keeps data, and how quickly a dead probe is noticed.
- [Linking with R1-MCP](https://docs.neuralconfig.com/probe-mcp/linking-with-r1-mcp/): Connect a Probe MCP account to R1-MCP so R1-MCP's Claude can reach your on-LAN ground truth — how the link is started from the R1-MCP side, what it grants, and how to revoke it.
- [Troubleshooting](https://docs.neuralconfig.com/probe-mcp/troubleshooting/): Fixes for common Probe MCP problems — activation failures, a probe that won't come Online, no telemetry arriving, the connector not authorizing, and code_mode timeouts or probe-offline errors.