Choosing an AI client
How Claude, ChatGPT, Codex, OpenCode and ZCode each connect to PopMCP, and why any client speaking Streamable HTTP needs only the one gateway URL.
PopMCP speaks the Streamable HTTP transport (MCP 2025-06) and acts as a full OAuth 2.1 authorization server, so any spec-compliant client works without special handling.
| Client | Auth | Set up with |
|---|---|---|
| Claude Desktop | OAuth | Custom connector |
| Claude Web | OAuth | Custom connector |
| ChatGPT | OAuth | Custom connector in developer mode, paid plans |
| Codex | OAuth | config.toml |
| OpenCode | OAuth | opencode.json |
| ZCode | OAuth | Settings → MCP Servers |
Your workspace's MCP page pre-fills copy-pasteable config for each of these.
What every client needs
https://app.popmcp.com/mcpThat is the whole configuration. There is no API key to paste. The client runs the OAuth flow itself and you approve connectors in the browser.
Any other client that implements remote MCP over Streamable HTTP takes the same URL and works the same way, even though it does not have its own page here.
If a client asks you to paste a token into its config file, it is using an older auth model. PopMCP is OAuth-only. Personal access tokens were removed.
Connect your first integration
What connector setups share and where they differ: an API key or an OAuth app, the exact callback URL, verification, and the account picker.
Connectors that need approval
Which integrations need vendor approval or a paid plan before they work, the usual wait and cost of each, and what you can build in the meantime.