What problem does it solve? Debugging MCP servers is difficult because the communication between AI clients and servers is invisible, making it hard to diagnose why tools are not called, calls hang, or capabilities mismatch. ## Core Features & Use Cases - Live Traffic Interception: Wrap any MCP server command with mcpsnoop to capture every JSON-RPC frame between your real client and server in an interactive TUI. - Filtering and Inspection: Filter frames by tool, method, direction, kind, and status, then drill into full request and response payloads. - Tool Call Replay: Replay any captured tool call against a fresh server instance to test fixes without restarting your client. - Use Case: Your Claude Desktop filesystem tool silently fails. Wrap the server with mcpsnoop, open the TUI, press 'c' to verify capability negotiation, filter with /tool:read_file, and discover the call hangs in PENDING state due to a permission error visible in stderr. ## Quick Start Wrap my MCP server launch command with mcpsnoop in my client config and open the mcpsnoop TUI to inspect the live traffic.