Skip to main content
Codex connects to Equip’s MCP server at https://equip.co/api/v3/mcp/ through its config file. The server is read-only, so Codex can look things up but never change them.

​
Add the Server

You need your organization’s API key in your shell as EQUIP_MCP first; see Connect Your AI Assistant to Equip.
1

Edit config.toml

Add this to ~/.codex/config.toml:
bearer_token_env_var names the variable, so Codex reads the key from your environment and the key itself never sits in the file.
2

Check the connection

Run codex mcp list in a terminal, or start Codex and ask “what tools do you have from equip?”.
3

Ask a question

Try: “Which of my job openings have the most candidates waiting in screening?”
The Connect your AI assistant section on the Account Developers page with the Codex tab selected, showing the export EQUIP_MCP line and the three-line config.toml entry with a copy button

The Codex snippet on the Developers page

  • 401 Invalid API key: the key was mistyped or rotated, or EQUIP_MCP is not exported in the shell you started Codex from. Run echo $EQUIP_MCP there.
  • 403 “isn’t included in your plan”: your plan does not include the MCP server. See Compare Plans, or contact support to have it switched on for your organization.
  • The server shows but has no tools: quit and restart Codex after editing the file.