Choosing an AI client
Which MCP clients work with PopMCP and what each supports.
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, Pro/Business/Enterprise |
| 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.