You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24-2Lines changed: 24 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Drop a <code>.pcap</code> file, ask questions in plain English — get answers b
39
39
40
40
## What is this?
41
41
42
-
Wireshark MCP is an [MCP Server](https://modelcontextprotocol.io/introduction) that wraps`tshark` into structured tools, letting AI assistants like Claude or Cursor perform deep packet analysis without you touching the command line.
42
+
Wireshark MCP is an [MCP Server](https://modelcontextprotocol.io/introduction) that turns`tshark` into a structured analysis interface, then layers in optional Wireshark suite utilities such as `capinfos`, `mergecap`, `editcap`, `dumpcap`, and `text2pcap` when they are available. The result is a packet-analysis server that still works with only `tshark`, but gets stronger automatically on hosts with more of the Wireshark toolchain installed.
43
43
44
44
```
45
45
You: "Find all DNS queries going to suspicious domains in this capture."
-`tshark` is the only required Wireshark CLI dependency
57
+
- Optional suite tools such as `capinfos`, `mergecap`, `editcap`, `dumpcap`, and `text2pcap` are auto-detected and enable extra MCP features when present
58
+
- Live capture prefers `dumpcap` when available, but falls back to `tshark` so a minimal installation still works
56
59
-`tshark` on your `PATH` is recommended, but `wireshark-mcp --install` also records detected absolute Wireshark tool paths for GUI clients
57
60
- Any [MCP-compatible client](https://modelcontextprotocol.io/clients): Claude Desktop, Claude Code, Cursor, VS Code, etc.
58
61
@@ -143,7 +146,7 @@ This detects all installed MCP clients and writes the config automatically. Exis
143
146
The generated entry always uses the current Python interpreter (`python -u -m wireshark_mcp.server`), forwards your current `PATH`, and stores detected absolute Wireshark tool paths when available, so GUI MCP clients do not need `wireshark-mcp` or `tshark` to be discoverable on their own.
144
147
145
148
> ⚠️ **Restart your MCP client** after running `--install` for changes to take effect.
146
-
> 🔎 If analysis tools still fail to launch, run `wireshark-mcp --doctor` to verify Python, `tshark`, and client config detection.
149
+
> 🔎 If analysis tools still fail to launch, run `wireshark-mcp --doctor` to verify Python, required vs optional Wireshark CLI tools, and client config detection.
147
150
148
151
### Manual Configuration
149
152
@@ -388,6 +391,7 @@ Your task is to diagnose network performance issues in <file.pcap>.
388
391
|`wireshark_security_audit`|**One-call security audit**: 8-phase analysis (threat intel, credential scan, port scan, DNS tunnel, cleartext, anomalies) with risk scoring (0-100) and recommendations |
389
392
|`wireshark_quick_analysis`|**One-call traffic overview**: file info, protocol distribution, top talkers, conversations, hostnames, anomaly summary, suggested next steps |
|`wireshark_get_capabilities`|**Toolchain capability report**: required, recommended, and optional Wireshark suite tools visible to the current MCP server |
391
395
392
396
> 💡 These tools replace the need to manually chain 5-10 tool calls. Just call one and get a complete report.
393
397
@@ -456,6 +460,23 @@ Your task is to diagnose network performance issues in <file.pcap>.
These tools are additive. The server still starts with only `tshark`, and only advertises or uses the extra workflows below when the corresponding Wireshark companion binaries are present.
469
+
470
+
| Tool | Description |
471
+
|---|---|
472
+
|`wireshark_editcap_trim`| Trim a capture to a timestamp window using `editcap`|
473
+
|`wireshark_editcap_split`| Split a capture by packet count or interval using `editcap`|
474
+
|`wireshark_editcap_time_shift`| Shift packet timestamps by a relative offset using `editcap`|
475
+
|`wireshark_editcap_deduplicate`| Remove duplicate packets using `editcap`'s duplicate window |
476
+
|`wireshark_text2pcap_import`| Convert ASCII or hex dumps into capture files using `text2pcap`|
477
+
478
+
</details>
479
+
459
480
<details>
460
481
<summary><b>Security Analysis</b></summary>
461
482
@@ -511,6 +532,7 @@ Your task is to diagnose network performance issues in <file.pcap>.
511
532
|`wireshark://reference/display-filters`| Complete display filter syntax cheatsheet with common examples |
512
533
|`wireshark://reference/protocol-fields`| Protocol field name reference for filters and extraction |
513
534
|`wireshark://guide/usage`| Recommended analysis workflows and tips |
535
+
|`wireshark://capabilities`| Current required, recommended, and optional Wireshark suite capabilities |
0 commit comments