mcp-client-testbench

armalite/mcp-client-testbench
★ 0 stars Python Code/Dev Tools Updated 2d ago
Controlled test rig for MCP client timeout and streaming behaviour. Spins up a configurable local MCP server (slow tools, progress notifications, SSE keep-alives, header logging) and runs headless Claude sessions against it to verify how the client handles long-running tool calls.
View on GitHub → 🔍 Audit Wallet Slippage →

Quick Install

Copy the config for your editor. Some servers may need additional setup — check the README.

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "mcp-client-testbench": {
      "command": "uvx",
      "args": [
        "mcp-client-testbench"
      ]
    }
  }
}

Or install with pip: pip install mcp-client-testbench

README Excerpt

**The question this repo answers:** when an MCP tool call takes a long time, what does the Claude client actually do, and does anything the server sends (progress notifications, keep-alives) stop it from timing out? **Why it exists:** Claude Code and Claude Cowork abort MCP tool calls that exceed a timeout (observed: 60 seconds for claude.ai connectors). Server

Tools (6)

CLAUDE_MODELDURATIONINTERVALMakefilePORTTIMEOUT_MS