Connecting ChatGPT & other AI apps

← Connecting Claude · Home · Next: Building Pages →

Divi Connect works with any AI app that speaks MCP, not only Claude. This page has the steps for ChatGPT, Codex, Gemini CLI, Antigravity, and any other MCP app such as Cursor, Cline, Roo Code, Zed or Windsurf. For Claude, see Connecting Claude.

Every address and command below is on your own site, ready to copy: open Divi Connect → Connection, pick your app, then choose how it signs in. The steps here match that screen.

Two ways to sign in #

Both work with every app:

Your AI app may use other words for these: choose OAuth for the first, or the option for an API key / no sign-in for the second.

ChatGPT #

Your site must be reachable from the internet. ChatGPT connects from its own servers, so a local address such as .local or localhost cannot work.

Sign in with WordPress (OAuth) #

1. In ChatGPT, open Settings → Plugins and press Browse directory at the top right.
2. Open the Add menu at the top right and choose Add custom MCP server.
3. Give it a name — Divi Connect does nicely — and, with Server URL chosen, paste the address from the Connection screen into Connection. This address carries no key.
4. Leave Authentication on OAuth. ChatGPT finds your site’s sign-in by itself; there is nothing to fill in under Advanced OAuth settings.
5. Tick I understand and want to continue, then press Create as a plugin. ChatGPT opens your site to sign in: use an administrator account and press Allow. Your name then appears under Connected people on the Connection screen.

Use the connector key #

1. In ChatGPT, open Settings → Plugins and press Browse directory at the top right.
2. Open the Add menu at the top right and choose Add custom MCP server.
3. Give it a name — Divi Connect does nicely — and, with Server URL chosen, paste the address from the Connection screen into Connection. On this route the address carries your key.
4. Set Authentication to No Auth.
5. Tick I understand and want to continue, then press Create as a plugin.

Codex #

Codex in VS Code and the Codex app share one configuration file, so you set it up once and both pick it up.

Sign in with WordPress (OAuth) #

1. In a terminal, run the command from the Connection screen. It looks like this, with your site’s address:
   codex mcp add divi-connect --url "https://yoursite.com/wp-json/divi-connect/v1/mcp"
2. Then run codex mcp login divi-connect. Your browser opens your site: sign in as an administrator and press Allow. If your Codex version has no login command, use the connector key instead.
3. Start codex and ask it to build something.

Use the connector key #

1. Run the command from the Connection screen in your terminal. It writes Codex’s configuration for you, which is safer than editing it by hand. The key travels inside the address, so there is nothing else to set up.
2. Check it with codex mcp list, then ask Codex to build something.

Terminal says codex is not recognized? Codex keeps its own copy and does not add it to your PATH. That is normal, and it is the same for the VS Code extension and the app. Either add Codex to your PATH, or open Codex and ask it to run the command for you; it can find its own copy.

Scripting it with codex exec? Add --approve-for-me. Without it, Codex cancels every tool call before it runs and reports “user cancelled MCP tool call”, which looks like the connector is broken. Interactive codex asks you instead.

Setting it up in Codex’s own MCP settings screen? That screen has a Headers field. Use the short address (the one without a key) and add one header: name Authorization, value Bearer followed by a space and your key. Both are on the Connection screen.

Do not paste your key into “Bearer token env var”. That box wants the name of an environment variable, not the key. With the key in it, Codex looks for a variable of that name, finds nothing and sends no key — it shows as connected and every call fails. Use the Headers field, or leave that box empty.

Gemini CLI and Antigravity #

They look like one app but they are not: each keeps its own configuration file, in its own format. Use the steps for the one you are running. Gemini CLI can sign in with OAuth; Antigravity cannot yet, so use the connector key for it.

Gemini CLI — Sign in with WordPress (OAuth) #

1. Add the block from the Connection screen to ~/.gemini/settings.json. If the file already has an mcpServers block, merge it into that.
2. Start gemini and type /mcp auth divi-connect. Your browser opens your site: sign in as an administrator and press Allow.
3. Ask it to build something.

Gemini CLI — Use the connector key #

1. Run the command from the Connection screen in your terminal. It writes the configuration for you, which is safer than editing JSON by hand.
2. Check it with gemini mcp list. You want a tick and the word Connected.

It says Disabled instead? Gemini CLI turns off every MCP server in a folder it does not trust, including ones you set up for your whole account. Run it from a folder you have trusted, and look for the “this folder is untrusted” line above the list.

Prefer to edit the file yourself? It is ~/.gemini/settings.json, and the address goes in a field called url, with your key in a headers section. The Connection screen shows the exact block.

Antigravity — Use the connector key #

1. Antigravity reads a different file — ~/.gemini/config/mcp_config.json — and calls the address serverUrl. Copy the block from the Connection screen. It uses the long address, the one with your key in it: Antigravity has no way to send a key separately, so this is the only address that works for it.
2. Restart Antigravity, then open Additional Options (…) → MCP Servers to check it picked Divi Connect up.

Do not add a headers section for Antigravity. Its configuration has no field for one, so a key put there is never sent: it connects, then every request is refused.

Antigravity contacts your site a few seconds after it starts, before you ask it anything. The Connection status at the top of the Connection screen is read from your own site, so it is the reliable check, more than the app’s own list.

Any other MCP app #

Cursor, Cline, Roo Code, Zed, Windsurf, and anything else that speaks MCP, work today.

Sign in with WordPress (OAuth) #

1. Give the app the address from the Connection screen and choose OAuth if it asks how to sign in. It registers itself; there is no client ID to type.
2. When it opens your site to sign in, use an administrator account and press Allow.
3. If the app has no sign-in of its own (it only takes an address or a header), use the connector key instead — that works with everything. If it does sign in but asks for a client ID and secret, the Connection screen can make a pair for it. Copy both straight away; the secret is shown only once.

Use the connector key #

Most apps take a single address: use the one from the Connection screen that carries your key. If the app asks for a header instead, use the short address plus the header Authorization: Bearer <your key>.

Quick connect: the Connection screen also has a one-line instruction you can paste into any AI that can already browse or run commands; it sets itself up from that.

Stuck? #

Send us what the app showed you at [email protected] and we will tell you which of the two routes it wants. Other problems: see Troubleshooting & FAQ.