Connect Codex desktop

Connect the Codex app to Acquisity, then ask it to show your campaigns.

Use this guide for the Codex app on your computer. You do not need to write code or use a terminal. You will copy a small settings block into a file, save it, and restart Codex.

Using Codex in a terminal instead? Follow Connect Codex CLI. These instructions are for local Codex tasks, not ChatGPT's website or cloud tasks.

1. Copy your Acquisity key

In Acquisity, create a workspace API key. Select workspaces:read and campaigns:read. These let Codex show your campaigns without changing them.

Keep the key ready. It is a password for this connection: paste it only into the settings below, never into a chat message.

2. Open Codex's settings file

Codex keeps its connection settings in a file called config.toml, inside the .codex folder in your home folder. The desktop app and CLI share this file.

On a Mac:

Open Finder. Choose Go → Go to Folder from the menu at the top of your screen.
Paste ~/.codex/ and press Return.
Open config.toml in a plain-text editor, such as TextEdit. If using TextEdit, use Format → Make Plain Text if offered, and turn off Edit → Substitutions → Smart Quotes.

On Windows:

Open File Explorer. Paste %USERPROFILE%\.codex into its address bar and press Enter.
Right-click config.toml, choose Open with, then Notepad.

If the folder or file is missing, open Codex and sign in once, then check again. If needed, create a plain-text file named exactly config.toml in that folder, without a .txt ending. If your organisation manages Codex settings centrally, ask its administrator to add this connection.

3. Add Acquisity

Keep any settings already in the file. Add this block at the bottom. If an mcp_servers.acquisity block already exists, update that block instead of adding a second one.

[mcp_servers.acquisity]
url = "https://api.acquisity.ai/mcp"
http_headers = { Authorization = "Bearer YOUR_ACQUISITY_API_KEY" }

Replace only YOUR_ACQUISITY_API_KEY with your complete Acquisity key. Keep Bearer , including its space, and keep the straight quotation marks. Save the file.

This stores the key on your computer. Do not share the file or put it in a shared project. Codex also supports environment-variable credentials; the CLI guide shows that option.

4. Restart and try it

Quit Codex fully, then reopen it. Start a new local task. Paste this message:

Use Acquisity to list the workspaces I can access. Ask me which one to use, then show its campaigns and statuses. Do not change anything.

Allow the read-only tool request if Codex asks. You should see your workspace, then its campaigns after you choose it. A workspace with no campaigns can correctly return an empty list.

You do not need to press an OAuth Authenticate button for this connection. Your saved API key provides access.

If it does not connect

Acquisity is missing: check the file name, save it, fully restart Codex and start a new local task. Make sure you did not add the block to another project's settings.
Invalid configuration: check the straight quotes and remove any duplicate mcp_servers.acquisity block.
401 or 403: check the full key, its scopes and that Public API access is enabled for the workspace. More fixes.

Let Codex make changes later

Use a workspace key with campaigns:write only when you want Codex to change campaigns. That scope also permits launching and pausing live outreach. Start with the read-only setup above, then choose the permissions you need.

To disconnect, remove the Acquisity block and restart Codex. Revoke the key in Acquisity to stop it working in every client. Disconnecting does not pause campaigns already running.

Reference: OpenAI's MCP configuration guide.