Connect OrgMCP to ChatGPT

ChatGPT speaks Streamable HTTP MCP over OAuth 2.1. OrgMCP exposes a universal MCP URL for the public Apps / Plugins Directory and keeps per-workspace URLs for custom connectors and other clients.

Recommended: public Apps / Plugins Directory

Once OrgMCP is listed, open the ChatGPT Apps directory, connect OrgMCP, and complete the OAuth popup. ChatGPT uses:

https://app.orgmcp.io/mcp

After you sign in, OrgMCP asks which workspace to authorize if you belong to more than one. The access token is bound to that workspace via the JWT tenant_id claim (Resource Indicators / RFC 8707 — the token’s aud is the universal URL).

Custom connector (Developer Mode)

ChatGPT Pro / Team / Enterprise → Settings → Apps & Connectors → Advanced → Developer mode, then Create a connector. You can paste either:

Universal: https://app.orgmcp.io/mcp (workspace chosen at consent), or
Path-tenant: https://app.orgmcp.io/t/<your-workspace-slug>/mcp (fixed workspace in the URL — same slug as your dashboard).

Default scopes: mcp:read + mcp:tools. Revoke anytime from Connected apps or ChatGPT’s connector settings.

Try it

Ask ChatGPT to “Search the wiki for our incident-response runbook” or “List my OrgMCP knowledge sources”. It will pick up the OrgMCP tools and return cited results from the authorized workspace.

Troubleshooting

“Connector failed to register”. Your network may be blocking app.orgmcp.io. ChatGPT’s DCR call is a single POST to /api/oauth/server/register.
“Authorization failed”. Sign in with an OrgMCP account that is a member of the workspace you want to authorize.
“invalid_token” / audience mismatch. A token minted for /mcp cannot be reused on /t/<slug>/mcp and vice versa. Reconnect with the matching URL.

Under the hood

See the OAuth for MCP reference for discovery URLs, scopes, and the authorize sequence. Operator runbook for the public listing: docs/RUN-chatgpt-plugin-submission.md.