Connect to ChatGPT
Honest status first: ChatGPT’s support for remote MCP servers is narrower than Claude’s and changes often. There are two realistic paths today, depending on your ChatGPT tier.
Path A — Developer Mode / Connectors
Remote-MCP connector support is rolling out behind Developer Mode and workspace Connectors admin settings (Plus, Pro, and Business/Enterprise where enabled). Availability depends on your plan and whether your workspace admin has enabled custom connectors.
- Open Settings → Connectors (Business/Enterprise admins: Settings → Connectors → Advanced / Developer Mode) and choose Add custom connector or Create.
- For the MCP server URL, enter
https://mcp.pocketpart.io/mcp. - For authentication, choose OAuth if offered (you sign in to PocketPart and pick an org, same as Claude). If only an API key / Bearer token option is available, paste a PocketPart key created at API keys as
Authorization: Bearer pp_mcp_live_…. - Save, open a new chat, and enable the connector for that chat if prompted.
/docs/chatgpt-add-connector.png/docs/chatgpt-connector-auth.pngPath B — Custom GPT Actions (not recommended)
Custom GPT Actions are OpenAPI/REST tool calls, not MCP. PocketPart speaks MCP (JSON-RPC over Streamable HTTP), so you cannot point a GPT Action’s OpenAPI schema at /mcp and expect tools to appear. Use Path A.
The PocketPart connector shows as connected in ChatGPT’s tools/connectors panel, and asking ChatGPT to “use the PocketPart status tool” returns your org, plan, and packs.
Custom-connector availability varies by tier and admin policy; some ChatGPT surfaces only auto-invoke tools they classify as “search”/“fetch,” so a tool may be connected but not called unless you ask for it by name; and if OAuth isn’t offered in your build, use a static pp_mcp_key. OpenAI relabels these menus frequently — verify against your tier.
Stuck? See Troubleshooting or validate your key with curl.