Getting started

Getting to a working setup is four steps: sign in, enroll a probe, deploy it on the customer LAN, and connect Claude.

1. Sign in

Go to the Probe MCP dashboard and Sign in with Google. Signing in creates your workspace. There is nothing to install to use the dashboard — the probe container comes later, and only runs on-site.

2. Enroll a probe

On the dashboard, click Enroll a probe, give the site a name (and an optional timezone, pre-filled from your browser), and click Provision probe.

You get back a one-line Docker command containing a single-use activation code that expires — mint it when you’re ready to run it. If it expires or you need a new one, use the New activation command button on the probes list.

3. Deploy the probe and point your network at it

Run that Docker command on a Linux host on the customer LAN that has Docker and outbound internet. The container activates itself, opens its outbound tunnel, and appears as Online in the dashboard with its LAN IP.

Then configure your network devices to send telemetry to that LAN IP — syslog, SNMP traps, and sFlow. Full detail:

• Deploying the probe
• Pointing your network at the probe

4. Connect Claude

Copy your MCP URL — https://probe-mcp.lanpulse.com/mcp — from the dashboard and add it to Claude as a custom connector. Claude walks you through a Google consent once, then code_mode appears in its tools.

• Connecting to Claude

Verify it works

Ask Claude:

Using Probe MCP, list my probes and show the last hour of syslog volume.

If the probe is Online and receiving events, you’ll get real data back. If not, see Troubleshooting.

Tip

Want the fastest payoff? Run the assessment_scorecard prompt once the probe is Online — it scans syslog, SNMP, and sFlow and produces a co-branded findings PDF.