OpenCode
Set up PopMCP as a remote server in your OpenCode config, for one repository or everywhere. No API key or headers: OpenCode runs OAuth on first use.
Add PopMCP under the mcp key in your OpenCode config. Use opencode.json in the project
root to scope it to one repository, or your global OpenCode config to make it available
everywhere.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"popmcp": {
"type": "remote",
"url": "https://app.popmcp.com/mcp",
"enabled": true
}
}
}"type": "remote" is what tells OpenCode this is a hosted server rather than a local
command. There is no headers block and no API key — PopMCP is OAuth-only, and OpenCode
runs that flow for you on first use.
Confirm
Start OpenCode. On the first run it opens PopMCP's consent screen in your browser, where you
tick the connectors to grant. Once approved, ask it to list_connections to see what it
received.
If you are editing a config that already has an mcp block, add popmcp alongside the
existing entries rather than replacing them.
Codex
Register PopMCP in ~/.codex/config.toml, sign in so Codex runs the OAuth consent in your browser and stores the token, then list servers to confirm.
ZCode
Add PopMCP to Z.ai's ZCode desktop app as an HTTP server, for your user or one workspace, with no headers or keys. Then approve what it can reach.