ChatGPT connector / about 5 minutes

Add Codex for Everything to ChatGPT.

One public MCP endpoint. ChatGPT handles discovery, opens the OAuth consent flow, and keeps the resulting token separate from your Site sign-in.

OAuth 2.1PKCE S256Read only

Setup

Four small steps.

Start in ChatGPT. You do not need to manually sign in to this Site first; OAuth will send you through sign-in when authorization is required.

  1. 01

    Turn on Developer mode

    In ChatGPT, open Settings, choose Security and login, then turn on Developer mode.

  2. 02

    Create the connection

    Open ChatGPT Plugins, select the plus button, and name the connection Codex for Everything. Choose a public MCP endpoint for the connection method.

  3. 03

    Paste the endpoint

    Paste the exact /api/mcp URL shown above, create the connection, and review the three read-only tools ChatGPT discovers.

  4. 04

    Authorize the first tool call

    Add the connection to a new chat and ask it to check connector status. ChatGPT will open the Codex for Everything consent flow. Sign in, review the scopes, and approve.

First test

Ask for status.

This is the smallest useful test because it triggers OAuth and confirms the MCP token made it back to the connector.

Check the Codex for Everything connector status.

What OAuth does

Two sign-ins, two different jobs.

Site sign-in identifies the person approving access. MCP OAuth issues the bearer token ChatGPT uses server to server. One does not replace the other.

  1. 01 / Discover

    ChatGPT reads the MCP and OAuth metadata.

  2. 02 / Sign in

    The Site identifies you for the consent screen.

  3. 03 / Approve

    OAuth issues a separate, scoped MCP access token.

  4. 04 / Use

    ChatGPT sends that token with each MCP request.

What gets access

Narrow by design.

Scopes

  • connector:status
  • capabilities:read

Tools

  • get_connector_status
  • search_capabilities
  • fetch_capability

Boundaries

  • No repository writes or Codex execution.
  • No voting, submissions, or webhooks.
  • No access token is stored in the browser page.

If it does not connect

Check these first.