Install
git clone https://github.com/alpadalar/netops-mcp.git
cd netops-mcp
uv venv
source .venv/bin/activate
uv pip install -e .Who it's for
If you want to attach ping, traceroute, mtr, nmap, DNS, HTTP and system monitoring to an MCP client, this service matches. Official text describes it as a server that exposes 26 network and system diagnosis tools, and it names Claude Desktop, Claude Code and Cursor.
Protocol notes:
https://modelcontextprotocol.io/
It suits people who can already clone a repository, use uv, and run Linux or macOS. Official text requires Python 3.10 or newer. The network tools are tied to the operating system and do not support Windows.
It does not fit people looking for a substitute path on Windows, nor people who nmap a public target on the first try. A scan actively probes a remote host; there is an operations and compliance boundary.
Official repository:
https://github.com/alpadalar/netops-mcp
First try in 3 minutes
There is only one official recommended path: after clone, make an environment with uv and do an editable install. Do not look for another installer, and do not switch to HTTP mode the first time.
git clone https://github.com/alpadalar/netops-mcp.git
cd netops-mcp
uv venv
source .venv/bin/activate
uv pip install -e .
Clone URL:
https://github.com/alpadalar/netops-mcp.git
Prerequisites: Python >= 3.10, uv, Linux or macOS. This page does not consecutively write a stdio start line. After install, put the entry that environment provides into the client; do not invent a command.
uv notes:
https://github.com/astral-sh/uv
After you connect, make one low-risk call: use the confirmed ping, and send probes only to a host you are allowed to probe. Do not call nmap, and do not turn on HTTP mode. ping leaves this machine over the network as packets.
Success: probe results come back, with no port scan and no HTTP listen. If install fails, first check that you are on Linux/macOS and that uv is available.
Use cases
Case 1: connectivity. The object is ping; the same group also has traceroute, mtr, telnet, netcat. The first time, use only ping. Evidence has no parameter table; success is probe output coming back. Do not probe unauthorized targets.
Case 2: DNS query. The objects are nslookup, dig, host. That is another class of read-only query. Query only domains you already know. Do not mix this with the HTTP group's curl, httpie, api_test as a first step. Evidence has no function-wrapper detail; only use the DNS tools the client actually shows.
Limits
HTTP mode needs an API key by default; without a key it refuses to start. Authentication notes:
https://github.com/alpadalar/netops-mcp#authentication
That is not the first-try path. nmap and system monitoring read or probe more information. The confirmation point is that you accept the probe scope and that local metrics will enter the conversation, then act. Do not invent unnamed listen addresses, key variables or Windows workarounds. Official text does not write uninstall steps.