NetOps MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NetOps MCP Server My Wi-Fi keeps disconnecting—run diagnostics and suggest fixes."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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_networkguides 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.10uv(recommended) or standardpython3 -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 sync2. Run Directly or with MCP Inspector
Test the server in stdio mode:
uv run python -m src.serverOr test interactively using the official MCP Inspector:
npx @modelcontextprotocol/inspector uv run python -m src.serverClaude 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 |
|
| Measures reachability, packet loss %, and average RTT latency. |
| None | Queries host routing table for default gateway and tests first-hop reachability. |
| None | Extracts host Wi-Fi interface state, SSID, signal %, and link rates via |
|
| Resolves hostnames via local resolver and measures DNS resolution latency in ms. |
|
| Extracts specific runbook remediation sections ( |
|
| Generates a unique incident ID ( |
|
| Queries past incident records to check for recurring failures or open tickets. |
Resources
URI | Description |
| Full operational SLA thresholds and bottom-up triage guidelines from |
Prompts
Prompt | Arguments | Description |
|
| Guides the LLM step-by-step through Layer 1 to Layer 3 diagnostic checks and incident escalation. |
Available Tools
7 toolscreate_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
Scored across 7 tools
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.
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.
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.
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
Related MCP Connectors
IP intelligence, network diagnostics, and AI service availability tools for AI agents.
Network, domain and website diagnostics for AI clients via MCP.
Free, no-API-key network lookups for AI agents — IP geolocation, DNS, WHOIS, HTTP and SSL/TLS certificate checks, and full domain health reports.
Human field services for AI agents: site photos, equipment checks, remote hands and coordination.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform real network diagnostics on the local machine, including ping, traceroute, DNS lookups, TLS checks, and more.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to debug local networks in plain language by pinging, sweeping subnets, tracing routes, resolving DNS, scanning ports, inspecting ARP tables and active connections, and checking URL reachability.MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to triage network incidents by fetching device telemetry, inspecting syslogs, and executing traffic reroutes through MCP tools.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to safely troubleshoot networks through read-only tools for device inventory, interface status, VLAN paths, BGP neighbors, route lookups, and interface error detection. Integrates with Microsoft Copilot Studio and Teams for natural-language-driven network diagnostics.-