mcp-spy

Debug and trace MCP server communication, latency, and protocol compliance.

Updated May 3, 2026
One-click install
npx skills add https://github.com/marktantongco/remotion-video-pro --skill mcp-spy-marktantongco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-spy
Source: https://github.com/marktantongco/remotion-video-pro/tree/main/skills/mcp-spy
Command: npx skills add https://github.com/marktantongco/remotion-video-pro --skill mcp-spy-marktantongco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

mcp-spy solves the problem of troubleshooting and debugging integrations with Model Context Protocol (MCP) servers by providing a detailed analysis of server communication, message traffic, latency issues, and protocol compliance.

Core Features & Use Cases

  • Debugging Communication: Inspect the traffic between Claude and MCP servers for errors, failed requests, and protocol violations.
  • Traffic Analysis: Monitor recent messages and filter traffic by message type to pinpoint specific issues.
  • Latency Analysis: Measure response times for various tools and detect latency warnings in logs.
  • Failed Request Analysis: Identify failures and parse error responses to determine common issues like connection issues, timeouts, or invalid JSON.
  • Server Debugging: Check server status, logs, and execute tools directly for troubleshooting.
  • Protocol Debugging: Inspect messages, validate requests, and validate JSON format to ensure protocol compliance.

Quick Start

Analyze the traffic logs of the MCP server using mcp-spy.

Frequently Asked Questions about mcp-spy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Model Context Protocol server communication errors?

Debug Model Context Protocol server communication errors by inspecting traffic between clients and servers to identify failed requests, connection issues, and protocol violations. mcp-spy analyzes message logs to pinpoint these integration failures.

What is the best way to monitor latency issues in MCP server integrations?

Monitor latency issues in MCP server integrations by measuring response times for tools and detecting latency warnings in server logs. This approach identifies slow-performing operations and highlights bottlenecks in server communication traffic.

How can I validate protocol compliance for Model Context Protocol messages?

Validate protocol compliance for Model Context Protocol messages by inspecting traffic details and checking JSON format validity. This ensures requests conform to expected specifications and helps identify malformed payloads causing integration failures.

Can I filter server traffic logs by message type to find failed requests?

Yes, you can filter server traffic logs by message type to isolate failed requests. mcp-spy parses error responses to determine common issues like timeouts, connection drops, or invalid JSON in the filtered message traffic.

What do I need to troubleshoot MCP server connections and execute tools directly?

Troubleshooting MCP server connections and executing tools directly requires log access and the ability to run MCP commands and scripts. This setup allows you to check server status, analyze traffic, and validate protocol messages.

Why does my MCP server return invalid JSON responses during integration?

MCP servers return invalid JSON responses during integration due to protocol violations or communication errors. Analyzing server traffic logs helps parse these error responses to determine if the issue stems from timeouts, connection failures, or malformed payloads.