MCP Debug is a debugging and development tool for Model Context Protocol (MCP) servers that enables rapid development and testing with features like hot-swapping, session recording, and automated playback testing.
From the registry: Debug and develop MCP servers with hot-swapping, session recording, and playback testing
$ uvx mcp-debug config initPlease install the `mcp-debug` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Create config.yaml** — Proxy config file listing servers to aggregate Run: `uvx mcp-debug config init`
Optional prerequisites:
- Install uv — uv/uvx required for the recommended Python-based launch (https://docs.astral.sh/uv/getting-started/installation/)
Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["mcp-debug","--proxy","--config","config.yaml"]
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.MCP_LOG_FILErequiredLog location.MCP_RECORD_FILErequiredAuto-record sessions.MCP_CONFIG_PATHrequiredDefault config file path.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.