Codex is OpenAI's coding agent. It runs in a terminal, in your editor and as a desktop app. Once Argorant is connected, you can ask Codex for market counts, contact lists, exports and campaigns in plain words, next to your code, and it uses your Argorant account and credits.
There are two ways in. The MCP connection is the one we recommend: Codex signs in to Argorant in your browser and gets Argorant's tools. The setup prompt is a shortcut for people who prefer an API key: you paste one prompt and Codex sets up the Argorant command line for itself.
Before you start
- You need an Argorant account with a confirmed email. No account yet? You can create one during the sign-in step.
- Run Codex on your own computer (the terminal app, the editor extension or the desktop app). A hosted Codex web task does not read your local MCP settings, so use the connection that task offers instead.
- In Argorant, open AI connections in the sidebar and pick the Codex tab. It shows the exact commands for your account.
Connect with the MCP commands (recommended)
- On the Codex tab, click Use AI connection settings. The tab first shows the setup prompt; this button switches to the MCP commands.
- Click Copy setup to copy both commands.
- Run them in a terminal on the same computer where Codex runs.
codex mcp add argorant --url https://mcp.argorant.com/mcp
codex mcp login argorant- The first command saves Argorant as an MCP server called
argorant. The second one opens your browser for the sign-in. - Sign in to Argorant. You see Argorant's permission screen. For Codex it usually says Connect Argorant to an app on this computer with a yellow note that Argorant cannot check the app. That is normal for apps that sign in through your own computer. If you just ran the command yourself, click Allow access.
- Go back to the terminal. Codex confirms the login.

Prefer clicking? In the Codex desktop app or the editor extension, open Settings, then MCP servers, then Add server. Choose Streamable HTTP, name it argorant and enter https://mcp.argorant.com/mcp. Then select Authenticate and finish the same browser sign-in. The terminal commands and the settings write the same entry, so use one or the other, not both.

Check that it works
- Restart Codex, or start a new session, so it loads the new server.
- Type
/mcpin Codex. Argorant should be listed with its tools. In a plain terminal,codex mcp listshows the saved servers too. - Start a new task with the request
Check my Argorant account.Codex callsargorant_accountand answers with your email, your role and the credits left.
Only that real answer proves the connection. A message like "connected" without your account details is not proof. On the Argorant side, the app now shows up under Settings, AI connections, Connected apps.
The setup prompt path
If you would rather work with an API key and the Argorant command line, stay on the first view of the Codex tab.
- Click Create private key. Argorant creates a personal key for this setup.
- Click Copy setup prompt. The prompt contains your new key, so paste it only into your own Codex session.
- Codex checks your account with the key, sets up
npx argorantand tells you when it is connected.

The key path works well, but the command line spends credits without asking when it runs inside an agent. Read the guardrails article before you let Codex run exports on its own.
Prompts to try
Check my Argorant account and tell me how many credits I have left.Free. Codex calls the account tool and reports.
Count CTOs at software companies in the Netherlands with 50 to 200 employees. Show five examples with names hidden.Free. Codex counts and previews, then suggests next steps.
Save that search as a list called NL CTOs. Do not reveal or export anything.Free. Codex saves the list and gives you the link to Lists.
Export the NL CTOs list to CSV. Tell me the row count and the most it can cost first, then wait for my yes.Codex states the cost and waits. After your yes it starts the export and checks it until the file is ready under Exports.
Common mistakes
- Running the commands on another machine. The MCP entry lives where you ran
codex mcp add. If Codex runs in a container or on a server, run the commands there. - Skipping
codex mcp login argorant. Without it the server is saved but not signed in, and Codex reports that it needs authentication. - Adding Argorant twice under different names. Keep one entry. If you already have one, log in again instead of adding another.
- Expecting mailbox orders in Codex. OpenAI apps do not get those tools. Do them in the Argorant app.
- Pasting the private setup prompt into a shared chat or a repository. It contains your key. If that happens, delete the key under Settings, API keys.
Remove Argorant from Codex
- Run
codex mcp logout argorantto drop the sign-in, thencodex mcp remove argorantto delete the entry. In the app or editor, remove it under Settings, MCP servers. - In Argorant, open Settings, AI connections and click Disconnect next to the app under Connected apps. Access ends at once.
- If you used the setup prompt, also delete that key under Settings, API keys.
Your lists, exports and campaigns stay in your Argorant account either way. Codex works on the same account as the web app, so everything it makes is there for you to check.