Test MCP servers like any other API
Choose MCP and enter the server's URL. Gostman loads its tools, resources, resource templates and prompts, and you call them with JSON arguments. Save the calls in a collection and add checks, so the same tests run in CI.
stdio:npx -y @modelcontextprotocol/server-everythingWhat it does
- Remote servers over Streamable HTTP, and local servers over stdio in the desktop app
- Call tool, read resource and get prompt, plus list operations that follow every page
- MCP 2026-07-28 and the revisions that start with initialize, back to 2024-11-05
- Sign in with OAuth, following the MCP authorization specification step by step
- Rule-based checks on tool definitions: missing descriptions, duplicate names and malformed input schemas
- A warning when a server's tools change between loads, so new instructions in a description do not slip by
- Tool errors count as failures in the collection runner and gostman run
Local commands are confirmed
The first time a stdio command runs, Gostman shows it and asks before starting it. The web app, gostman run and agent sessions never start local commands.