MCP Sniffer

Created By
shivdeepaka year ago
MCP Sniffer captures network traffic between MCP clients and servers and displays it in a web UI.
Overview

What is MCP Sniffer?

MCP Sniffer is a tool that captures network traffic between MCP clients and servers, displaying the data in a user-friendly web interface.

How to use MCP Sniffer?

To use MCP Sniffer, install it via pipx and run it as a reverse proxy between your MCP client and server. Access the web UI at http://127.0.0.1:8888 to visualize the captured traffic.

Key features of MCP Sniffer?

  • Captures request and response payloads between MCP clients and servers.
  • Provides a web UI for visualizing network traffic similar to Google Chrome DevTools.
  • Configurable listening and upstream host/port settings.

Use cases of MCP Sniffer?

  1. Debugging network issues in MCP applications.
  2. Analyzing communication patterns between clients and servers.
  3. Monitoring real-time data exchange in development environments.

FAQ from MCP Sniffer?

  • Is MCP Sniffer easy to set up?

Yes! Installation is straightforward using pipx, and the web UI is accessible after running the tool.

  • Can MCP Sniffer capture all types of network traffic?

MCP Sniffer is specifically designed for Model Context Protocol traffic, so it may not capture other types of network communications.

  • Is there a graphical interface for viewing the captured data?

Yes! MCP Sniffer includes a web UI for visualizing the captured network traffic.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shivdeepak
Star
1
Language
Python
License
GPL-3.0 license

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)

a day ago