Key Takeaways
- MCP Workbench gives Claude Code users a browser-based GUI to debug MCP servers: paste a command, see tools, test calls, and verify protocol compliance.
- Try it free at mcp-workbench.uk.
What Changed
MCP Workbench has opened its beta — a browser-based testing platform for Model Context Protocol servers. Think Postman for REST APIs, but for MCP. You no longer have to debug cryptic stdio errors inside Claude Desktop or a terminal. Instead, you open a browser tab, paste your server command, and get instant visibility into every tool, schema, and JSON-RPC message.
The beta is free and open now at mcp-workbench.uk. No credit card required. Early beta testers get free lifetime Pro access when paid tiers launch.
What It Means For You
If you build or use MCP servers with Claude Code, this changes your debugging workflow significantly. Here's what the beta includes:
- Instant Server Connection — Paste any MCP server command (e.g.,
npx -y @modelcontextprotocol/server-filesystem /tmp) and connect within seconds. Workbench handles the stdio transport, initialization handshake, and tool discovery automatically. - Visual Tool Catalog — See every tool your server exposes with its JSON Schema, descriptions, and required parameters. No more guessing what arguments a tool expects.
- Form-Based Tool Testing — Fill out tool parameters in auto-generated forms instead of hand-crafting JSON payloads. Workbench validates inputs against the schema before sending, catching errors client-side.
- Live JSON-RPC Console — Inspect every request and response in full. Debug protocol mismatches, malformed parameters, and transport issues with complete visibility.
- Multi-Client Compatibility Checks — Test how your server behaves across Claude Desktop, Cursor, VS Code, and Cline emulators. Catch client-specific compatibility issues before your users do.
- Saved Configurations — Save and share server configurations with your team. Export to JSON or share a direct link. Everyone tests the same setup.
- Hermes Verification Engine — Every connected server is automatically validated for protocol compliance, schema integrity, error handling, and cross-client compatibility. Get a pass/fail report in seconds.
Try It Now
- Visit mcp-workbench.uk and open the live demo.
- Paste your MCP server command — try
npx -y @modelcontextprotocol/server-filesystem /tmpto start. - Browse the tool catalog, test a tool with the form, and check the JSON-RPC console.
- Run the Hermes verification to get a compliance report.
- Sign up for beta access to unlock advanced features.
This is especially valuable for Claude Code users who rely on MCP servers for tool access. Instead of adding a server to your claude mcp add config and hoping it works, you can validate it first in Workbench — catching schema errors, handshake failures, and compatibility issues in minutes instead of waiting for bug reports.
The roadmap includes CI/CD webhook integration, a public MCP server directory, team workspaces, and performance profiling. For now, the beta is a solid, free tool to add to your MCP debugging arsenal.
Source: dev.to
[Updated 07 Aug via devto_mcp]
The new source adds a critical market context: with 1000+ community MCP servers now available, most ship without any verification, creating a 'verification gap' that MCP Workbench directly addresses. The article details five specific failure points—protocol compliance, schema integrity, error handling, cross-client compatibility, and response quality—that Workbench's Hermes engine is designed to catch. This positions the beta not just as a debugging convenience but as a necessary safeguard for production deployments, especially as developers increasingly install servers from npm, PyPI, or GitHub without independent validation. [per MCP Workbench]
