Skip to content
MCP server

tshark-mcp

Read-only packet capture analysis with tshark, including Diameter, GTP and SIP

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI
Runs
Locally
Version
0.4.0
Listing updated
today

Similar MCP servers

About tshark-mcp

tshark-mcp is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

Point it at a folder of pcap files and ask what went wrong. An incident_summary tool runs every check the capture's protocols allow, ranks the findings and suggests the next call, and every claim cites frame numbers that can be opened in Wireshark.

Beyond DNS, TCP and TLS problems, it pairs requests with answers across Diameter, GTP, PFCP, SIP, RTP, SIGTRAN and MAP, names cause codes with their 3GPP references and can follow one subscriber across protocols. The author says it was built by a mobile core engineer, and reports testing against 102 public captures with 1,064 tool calls.

It is deliberately constrained: no shell, no live capture, and no writes except an optional export_subset directory you enable. The server refuses to start unless TSHARK_MCP_ALLOW_DIRS is set, applies caps on size, packets, output and time, and can pseudonymise IMSIs, phone numbers and IPs. It has 63 tools, with 34 in the default set, and needs tshark 4.0 or newer.

Install

Run in a terminal

claude mcp add tshark-mcp --env TSHARK_MCP_ALLOW_DIRS='<TSHARK_MCP_ALLOW_DIRS>' -- uvx tshark-mcp-server

Add to claude_desktop_config.json

{
  "mcpServers": {
    "tshark-mcp": {
      "command": "uvx",
      "args": [
        "tshark-mcp-server"
      ],
      "env": {
        "TSHARK_MCP_ALLOW_DIRS": "<TSHARK_MCP_ALLOW_DIRS>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "tshark-mcp": {
      "command": "uvx",
      "args": [
        "tshark-mcp-server"
      ],
      "env": {
        "TSHARK_MCP_ALLOW_DIRS": "<TSHARK_MCP_ALLOW_DIRS>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "tshark-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "tshark-mcp-server"
      ],
      "env": {
        "TSHARK_MCP_ALLOW_DIRS": "<TSHARK_MCP_ALLOW_DIRS>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "tshark-mcp": {
      "command": "uvx",
      "args": [
        "tshark-mcp-server"
      ],
      "env": {
        "TSHARK_MCP_ALLOW_DIRS": "<TSHARK_MCP_ALLOW_DIRS>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "tshark-mcp": {
      "command": "uvx",
      "args": [
        "tshark-mcp-server"
      ],
      "env": {
        "TSHARK_MCP_ALLOW_DIRS": "<TSHARK_MCP_ALLOW_DIRS>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • TSHARK_MCP_ALLOW_DIRSDirectories the server may read captures from, colon-separated. Required: the server refuses to start without one.Required
  • TSHARK_MCP_TSHARKPath to the tshark binary (4.0 or newer) when it is not on PATH.
  • TSHARK_MCP_REDACTPseudonymise identifiers in every result: ids (IMSI, MSISDN, IMEI, SIP users, UE IPs) or ids+ips (every IP too).
  • TSHARK_MCP_EXPORT_DIRTurns on export_subset: the one directory it may write new pcapng files to. Must not overlap an allowed dir. Unset: the server writes nothing.

Tools this server provides (2)

Taken from the project documentation; the running server may differ.

incident_summary
Runs the applicable checks, ranks findings and suggests the next call.
export_subset
Writes a filtered pcapng to the enabled export directory.

What it does

Incident summary
Ranks findings from a capture and names the next call.
Telecom protocols
Covers Diameter, GTP, PFCP, SIP, RTP, SIGTRAN and MAP.
Frame-numbered answers
Each claim points to frames you can open in Wireshark.
Restricted access
Reads only files inside allowed directories under hard caps.
Optional redaction
Pseudonymises identifiers and optionally every IP address.
Subscriber tracing
Follows one subscriber across protocols.

Good for

  • Find why a Diameter or GTP session failed
  • Diagnose one-way audio in a SIP/RTP call
  • Investigate slow servers or TLS and DNS errors
  • Share captures with an assistant with identifiers redacted

Pricing

Open source

MIT licence.

tshark-mcp FAQ

Can it capture live traffic?

No. It only runs tshark -r on existing files.

What do I need installed?

uv and tshark 4.0 or newer.

How many tools does it have?

63, with a default set of 34 to keep the list short.

What licence is it?

MIT.

Is tshark-mcp free?

Yes. tshark-mcp is open source, so you can use and self-host it for free.

How do I add tshark-mcp to Claude Code?

Run this command in your terminal: claude mcp add tshark-mcp --env TSHARK_MCP_ALLOW_DIRS='<TSHARK_MCP_ALLOW_DIRS>' -- uvx tshark-mcp-server

What are the best alternatives to tshark-mcp?

The closest alternatives to tshark-mcp are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers