MCP server wrapper for WireMCP — AI-assisted real-time network traffic analysis via Wireshark/tshark.
WireMCP is a Model Context Protocol server that connects AI assistants to Wireshark (via the tshark command-line tool) for real-time network traffic capture and analysis. It enables AI-driven packet inspection, protocol analysis, traffic filtering, and network troubleshooting without leaving the chat interface. See bstefanescu/wiremcp for full documentation. No API keys are required, but tshark must be accessible and the container may need elevated network privileges to capture live traffic.
| Tool | Description |
|---|---|
wiremcp_info | Return status information for the WireMCP server |
Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:
docker-compose up -d
docker run -i --rm hackerdogs/wiremcp-mcp:latest
docker run -d -p 8458:8458 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_PORT=8458 \
hackerdogs/wiremcp-mcp:latest
Add to your Claude Desktop or Cursor MCP config:
{
"mcpServers": {
"wiremcp-mcp": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT", "hackerdogs/wiremcp-mcp:latest"],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}
First, start the server using Docker Compose or docker run with HTTP mode (see Deploy above), then point your MCP client at the running server:
{
"mcpServers": {
"wiremcp-mcp": {
"url": "http://localhost:8458/mcp"
}
}
}
When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport mode: stdio or streamable-http |
MCP_PORT | 8458 | HTTP port (only used with streamable-http) |
The fastest way to get started is through Hackerdogs:
Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly (e.g. "Use naabu to scan example.com"). If you don't specify, Hackerdogs will automatically choose the best tool for the job — it may choose this one on its own.
Want to contribute or chat with the team? Join our Discord.
docker build -t hackerdogs/wiremcp-mcp:latest .
./test.sh
1. Start the server in HTTP mode:
docker run -d --rm --name wiremcp-mcp-test -p 8458:8458 \
-e MCP_TRANSPORT=streamable-http \
hackerdogs/wiremcp-mcp:latest
2. Initialize the MCP session:
SESSION_ID=$(curl -s -D - -X POST http://localhost:8458/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')
curl -s -X POST http://localhost:8458/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
3. Call a tool:
curl -s -X POST http://localhost:8458/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"run_wiremcp","arguments":{"arguments":"--help"}}}'
4. Clean up:
docker stop wiremcp-mcp-test
You can run the Wiremcp CLI in the same container by overriding the entrypoint without starting the MCP server.
Show help:
docker run -i --rm --entrypoint wiremcp hackerdogs/wiremcp-mcp:latest --help
Content type
Image
Digest
sha256:e14c0a994…
Size
74.8 MB
Last updated
3 months ago
docker pull hackerdogs/wiremcp-mcp