Paste a server URL and watch GPT-5 call your tools in a real conversation — before you wire it into Developer Mode, the Responses API, the Agents SDK or Codex CLI, each of which fails differently.
Paste a server URL, pick a model, and watch it call your tools in a real conversation. No install.
No server of your own? Leave it blank and use one of the public mock servers.
OpenAI has the broadest MCP surface of any vendor and the most ways to get it subtly wrong. ChatGPT Developer Mode, the Responses API’s mcp tool, the Agents SDK and Codex CLI all reach MCP servers, with different permission models — most notably an asymmetry between read-only and write tools that is easy to miss until a write silently does not happen. Testing the tool calls in isolation first tells you whether a failure is your server, your schema, or the integration path you picked.
OpenAI converts your MCP tools into function definitions, and then each integration path applies its own permission layer on top. The conversion is the same everywhere; the permissions are not. That is why the failure people report as 'GPT ignored my tool' is usually a path-level restriction rather than anything the model decided.
Call a write-capable tool on the complex-schema mock here, where no permission layer applies. If it succeeds here and silently no-ops in the ChatGPT app, you have found the read-only asymmetry rather than a bug. All the mock servers →
| Model | Model ID | Credits / run |
|---|---|---|
| GPT-5.4 nano | openai/gpt-5.4-nano | 2 |
| GPT-5.4 mini | openai/gpt-5.4-mini | 4 |
| GPT-5 mini | openai/gpt-5-mini | 4 |
| GPT-5.3 Codex | openai/gpt-5.3-codex | 12 |
| GPT-5.4 | openai/gpt-5.4 | 12 |
| GPT-5 | openai/gpt-5-chat | 12 |
| GPT-5.5 | openai/gpt-5.5 | 15 |
| GPT-5.6 Luna | openai/gpt-5.6-luna | 6 |
| GPT-5.6 Luna Pro | openai/gpt-5.6-luna-pro | 6 |
| GPT-5.6 Terra | openai/gpt-5.6-terra | 12 |
| GPT-5.6 Terra Pro | openai/gpt-5.6-terra-pro | 12 |
| GPT-5.6 Sol | openai/gpt-5.6-sol | 15 |
| GPT-5.6 Sol Pro | openai/gpt-5.6-sol-pro | 15 |