Free MCP tester that runs entirely in your browser. Paste any MCP server URL and inspect every tool, prompt, and resource — then call them with real arguments and see live JSON-RPC traffic. Works with HTTP + SSE and Streamable HTTP servers.
Want to test it with an AI?
See exactly how Claude, GPT and Gemini call your tools in real conversations — then save the setup as a reusable agent.
✦ Free credits on sign-up · no credit card
Need a quick security check too?
Test for HTTPS, authentication, security headers, CORS and 14 more — free MCP server security audit.
MCP weekly digest
New servers, security advisories, and tutorials — straight to your inbox. No spam.
An MCP tester is a tool that connects to a Model Context Protocol server, lists everything the server exposes (tools, prompts, resources), and lets you call those capabilities with real input — so you can verify the server actually does what its schema promises before wiring it into Claude Desktop, Cursor, or Claude Code.
This MCP tester runs entirely in your browser. There is nothing to install, no CLI to configure, and no API keys to manage. Paste a URL, click connect, and you are testing.
https://mcp.example.com/sse or a Streamable HTTP endpointinitialize handshake and lists capabilitiesNeed a server to point at? Browse the MCP servers directory for live remote endpoints.
tools/list and renders each tool with its input schematools/call with the arguments you provide, surfaces errors verbatimprompts/list and prompts/get outputresources/readThe two terms get used interchangeably. The official MCP Inspector from Anthropic is a local Node tool you run with npx @modelcontextprotocol/inspector. This in-browser MCP inspector online does the same job for remote (HTTP / SSE / Streamable HTTP) servers — without any local setup.
For STDIO servers that run as a child process on your machine, use the local inspector. For everything else, paste the URL above.
Enter a server URL to explore its tools, prompts, and resources
Connection details
Tokens are never stored — sent directly to the server per request. Use test/expirable tokens.