Skip to main content
Glama

NetOps MCP Server

A Model Context Protocol (MCP) server providing structured, bottom-up network diagnostics (OSI Layers 1–3) for LLM clients like Claude Desktop.


Key Highlights

  • WSL2 Host Boundary Traversal: WSL2 runs inside a virtualized Hyper-V switch. Standard Linux utilities cannot see host Wi-Fi or physical adapters. This server bridges across the boundary into Windows host binaries (netsh.exe, route.exe) to collect physical Wi-Fi signal, link rates, and default gateway status.

  • Complete MCP Primitive Coverage:

    • Tools: Active diagnostic probes (run_ping, get_gateway_telemetry, get_wifi_telemetry, resolve_dns, lookup_remediation, create_incident_ticket).

    • Resources: Exposes standard-backed runbooks (netops://runbooks/network-triage) directly into the agent's context window.

    • Prompts: triage_network guides the LLM through a disciplined, bottom-up diagnostic sequence rather than jumping to conclusions.

  • Defensive Engineering:

    • Strict input validation against command chaining (;, |, &, etc.) and option-injection flags (-).

    • Hard timeouts on all subprocess network calls (ping, netsh, route).

    • SQLite persistence for tracking triage incidents locally without crashing server responses on I/O failures.


Related MCP server: Pingo

Setup & Installation

Prerequisites

  • Python >= 3.10

  • uv (recommended) or standard python3 -m venv

1. Clone & Install Dependencies

git clone https://github.com/drew-1618/netops-mcp.git
cd netops-mcp

# Using uv (fast, deterministic sync from uv.lock)
uv sync

2. Run Directly or with MCP Inspector

Test the server in stdio mode:

uv run python -m src.server

Or test interactively using the official MCP Inspector:

npx @modelcontextprotocol/inspector uv run python -m src.server

Claude Desktop Integration (Windows + WSL)

Add the server to your Claude Desktop configuration file (%APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "netops": {
      "command": "wsl.exe",
      "args": [
        "-e",
        "/<your-absolute-path>/netops-mcp/.venv/bin/python",
        "-m",
        "src.server"
      ]
    }
  }
}

Note: Claude Desktop will automatically launch and manage the background WSL process over stdio. No terminal or WSL window needs to remain open.


MCP Reference

Tools

Tool

Arguments

Description

run_ping

target: str, count: int = 3

Measures reachability, packet loss %, and average RTT latency.

get_gateway_telemetry

None

Queries host routing table for default gateway and tests first-hop reachability.

get_wifi_telemetry

None

Extracts host Wi-Fi interface state, SSID, signal %, and link rates via netsh.exe.

resolve_dns

hostname: str

Resolves hostnames via local resolver and measures DNS resolution latency in ms.

lookup_remediation

category: str

Extracts specific runbook remediation sections (physical, packet_loss, latency, dns).

create_incident_ticket

target, failing_layer, summary, severity

Generates a unique incident ID (INC-XXXXXXXX) and records it in SQLite.

query_incident_history

target: Optional[str], status: Optional[str], limit: int = 5

Queries past incident records to check for recurring failures or open tickets.

Resources

URI

Description

netops://runbooks/network-triage

Full operational SLA thresholds and bottom-up triage guidelines from runbooks/network_triage_guide.md.

Prompts

Prompt

Arguments

Description

triage_network

target_host: str = "8.8.8.8"

Guides the LLM step-by-step through Layer 1 to Layer 3 diagnostic checks and incident escalation.

Available Tools

7 tools
create_incident_ticketC

Creates a structured operational incident ticket payload for escalation

Inputs: target (required), summary (required), failing_layer (required), severity. Returns: result

get_gateway_telemetryB

Discover the local default gateway and check first-hop reachability.

Inputs: no named parameters.

get_wifi_telemetryA

Gathers local WiFi interface telemetry such as SSID, signal strength percentage, radio type, and link rates.

Inputs: no named parameters.

lookup_remediationA

Look up specific remediation advice and thresholds from the triage runbook.

Valid categories: 'physical' (or 'signal', 'L1'), 'packet_loss' (or 'loss'), 'latency' (or 'RTT', 'bufferbload').

Inputs: category (required).

query_incident_historyA

Queries past incident tickets to identify recurring failures, historical context, or open issues

Inputs: limit, status, target. Returns: result

resolve_dnsA

Resolves a hostname using the local system resolver & measures resolution latency

Inputs: hostname (required). Returns: result

run_pingB

Pings an IP address or hostname to check reachability, average latency, and packet loss.

Inputs: target (required), count.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct diagnostic or operational action: gateway telemetry, WiFi telemetry, ping, DNS, runbook lookup, and incident creation/history. The only possible overlap is reachability checks between get_gateway_telemetry and run_ping, but their scopes are explicitly separated by first-hop vs arbitrary target.

    Naming Consistency5/5

    All tools follow a verb_noun snake_case pattern such as get_*, run_*, resolve_*, create_*, query_*, and lookup_*. There is no mix of casing or grammatical styles, and each verb clearly signals the tool's intended action.

    Tool Count5/5

    Seven tools is a focused, appropriately scoped set for a NetOps assistant: four network diagnostics, one remediation reference, and two incident-management tools. Each tool adds a distinct capability without unnecessary bloat.

    Completeness4/5

    The set covers the core diagnostic loop with gateway/WiFi/ping/DNS checks, remediation lookup, and incident creation/history. It lacks some obvious extras like traceroute or incident update/close, but these are workable gaps rather than blocking omissions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers