Frequently Asked Questions
What is the MCP Test Client?
The MCP Test Client is a free browser-based tool for validating any MCP (Model Context Protocol) client implementation against four hosted mock servers — echo, auth, error, and complex. Use it to verify your client handles connections, capability negotiation, tool discovery, tool execution, authentication, and error paths correctly before pointing it at production servers.
Is the MCP Test Client free?
Yes, completely free. No sign-up, no API key, no install, no rate limit. Run as many test sessions as you need, against any of the four hosted mock servers.
What mock MCP servers are available?
Four hosted mock servers: Echo (returns whatever you send — basic connectivity and message-handling tests), Auth (requires Bearer-token auth — exercises your auth flow), Error (deliberately returns protocol errors, timeouts, and edge-case responses — validates your error handling), and Complex (multiple tools with different schemas — tests parameter validation and tool selection).
What does my MCP client need to handle?
A robust MCP client should handle the connection lifecycle (initialize, maintain, close cleanly), capability negotiation, tool discovery and caching, tool execution with proper argument shapes, error handling (network, timeout, protocol), and authentication including credential refresh. The four mock servers exercise each of these areas explicitly.
Which transports does the MCP Test Client support?
The hosted mock servers support HTTP, SSE, and Streamable HTTP — the modern MCP transports defined by the 2025-11-25 spec revision. Stdio is not exposed by the hosted mocks since stdio is a local-only transport.
How is this different from the MCP Server Tester?
The MCP Test Client validates that your client code speaks MCP correctly — it gives you mock servers to talk to. The MCP Server Tester does the opposite: it acts as a client so you can test your own MCP server. Use both during development: Test Client for client implementations, Server Tester for server implementations.
Can I test my MCP client with real AI models after?
Yes. After validating against the mock servers, point MCP Agent Studio at any MCP server URL to see how Claude, GPT-5, Gemini, GLM, Qwen, and Grok actually call your tools — useful for catching tool-selection drift before shipping.