MCP client
Everything a Model Context Protocol server exposes, in one tab.
Connect over Streamable HTTP, legacy SSE or stdio (Testnizer starts the local server for you). Testnizer negotiates protocol 2024-10-07 through 2026-07-28 — leave it on Auto, force Legacy, or pin a version per tab — and when a server asks for more input mid-call, it shows a form for it.
- Tools with a form built from each tool’s JSON Schema (and a JSON toggle), Resources with templates, Prompts and Notifications
- A raw JSON-RPC frame view of everything on the wire, the handshake included, plus the negotiated version and server instructions
- No Auth, Basic, Bearer, API Key or OAuth 2.1 — with a step-by-step OAuth 2.1 debugger: metadata, dynamic client registration, PKCE, sign-in, token exchange
- Custom HTTP headers and stdio environment variables, with {{variables}}; paste or export the config for VS Code, Cursor and Claude Desktop
- Save with Ctrl+S, add Tests and Scripts (pm.test, pm.expect, pm.mcp), and run MCP requests in the Runner, a Test Suite or a schedule
This connects to the MCP server you point it at. OAuth tokens, the PKCE verifier and the client secret stay in the app’s main process and are never saved. A run only starts a stdio server whose exact command you have connected to once on this computer.
Read the docs