ChatGPT

ChatGPT supports MCP via the Developer Mode beta. Like Claude.ai, it uses OAuth 2.1 + Dynamic Client Registration — no static API key paste flow inside ChatGPT.

Developer Mode is in beta on Plus, Pro, Business, Enterprise, and Edu plans. Important capability gap: Plus / Pro individual users get read/fetch-only MCP even with Developer Mode on. Full write actions (track_keyword, update_listing, localize_listing, simulate_metadata_only, …) require a Business, Enterprise, or Edu workspace.

Setup (individual: Plus / Pro)

Enable Developer Mode

chatgpt.com → profile picture → Settings → Connectors → scroll down → Advanced → toggle Developer mode on.

Add a custom connector

Same Connectors page → Create (top right).

Name: Forvibe
MCP Server URL: https://www.forvibe.app/mcp
Authentication: OAuth (ChatGPT discovers Forvibe's auth server automatically via the well-known endpoints).
Check I trust this application to confirm.

Approve in browser

ChatGPT opens forvibe.app/oauth/authorize. Sign in if needed, review scopes, click Approve.

Setup (Business / Enterprise / Edu)

Workspace admins need to grant Developer Mode before individual users can add custom connectors.

Admin: enable Developer Mode for the workspace

Workspace Settings → Permissions & Roles → Connected Data → Developer mode / Create custom MCP connectors → on. Use RBAC to scope it to specific roles if needed.

User: add the connector

Same flow as individual users (Settings → Connectors → Create + the form above). Write actions are unlocked automatically by the workspace plan.

Verify

Start a new chat. Ensure a tool-capable model is selected (GPT-5 or GPT-4o). Ask: "Use Forvibe to list my projects." Confirm the first tool call. For write actions, ChatGPT shows a confirmation modal before each call — that's a feature, not a bug.

ChatGPT's MCP integration is still labeled beta. If the OAuth loop stalls or returns 401, the Troubleshooting guide covers the most common fixes.