How an 8MB MCP Tool Response Crashes Claude Code — And How to Debug Prompt Cache Misses Across Agents A developer released three open-source, zero-telemetry tools for debugging Model Context Protocol (MCP) failures in coding agents such as Claude Code, OpenAI Codex CLI, Cursor and VS Code Copilot. The tools target three silent failure modes: oversized tools/list responses that exhaust context, tools/call outputs large enough to tear down the stdio pipe (Claude Code's 8 MiB limit, Codex's 16 MiB), and prompt-cache misses caused by mid-session config edits. The packages are @framy2/ctxwise (context firewall, multi-editor MCP auditor and CI budget guard), @framy2/mcp-diet (a stdio MCP proxy that offloads large results and redacts secrets) and @framy2/agent-wire-tap (a wire contract tester with a --passthrough prompt-prefix cache-miss debugger). If you use Claude Code , OpenAI Codex CLI , Cursor , or VS Code Copilot with Model Context Protocol MCP servers, your context window and prompt cache are exposed to three silent failure modes: tools/list : github , postgres , playwright injects tools/call :