Sharkmcp

Created By
kriztalza year ago
A tshark MCP server for packet capture and analysis Features: Async: your agent can run a curl command and get the packets for it Flexible: You choose the capture and display filters Config: You can reuse the display and capture filters
Overview

What is SharkMCP?

SharkMCP is a Model Context Protocol (MCP) server designed for network packet capture and analysis, integrating with Wireshark/tshark to facilitate network security analysis, troubleshooting, and packet inspection.

How to use SharkMCP?

To use SharkMCP, clone the repository, install dependencies, and run the server. You can start a packet capture session, run your tool or request, and then stop the capture to analyze the results.

Key features of SharkMCP?

  • Async packet capture with configurable filters
  • Analyze existing PCAP files
  • Flexible output formats (JSON, custom fields, text)
  • SSL/TLS decryption support
  • Reusable configurations for capture and analysis

Use cases of SharkMCP?

  1. Debugging programs by capturing and analyzing network requests.
  2. Monitoring HTTPS traffic and decrypting it for analysis.
  3. Performing network security assessments and troubleshooting network issues.

FAQ from SharkMCP?

  • What are the system requirements?

Wireshark/tshark must be installed, along with Node.js (version 18+) and pnpm as the package manager.

  • How do I install SharkMCP?

Clone the repository, install dependencies, build the project, and run the server.

  • Can I use SharkMCP for real-time packet analysis?

Yes, SharkMCP allows for real-time packet capture and analysis.

Server Config

{
  "mcpServers": {
    "sharkmcp": {
      "command": "node",
      "args": [
        "/path/to/SharkMCP/dist/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kriztalz
Star
-
Language
-
License
-
Category
monitoring

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago