How to Use Every with Codex

Every , Product team

Published · 2 min read

Read as Markdown

You finish with a Codex MCP connection to Every and an inspected live business record.

Read Every’s agent setup reference
Table of Contents

Codex can use Every through a Streamable HTTP MCP connection. Configure the hosted endpoint, authorize your account in the browser, and verify a read-only result before you request business changes.

Codex uses config.toml for MCP configuration. A Claude-style .mcp.json file is not the configuration path for this guide. The Every endpoint is https://admin-mcp.every.ai/mcp.

What you need

Use a current Codex client with MCP support and an environment that can reach Every’s server and complete browser authorization. Check any workspace policy that controls external tools.

You need access to your intended Every account. Authorization happens in the browser. Do not put passwords, one-time codes, tokens, or invented API keys into your prompt or a shared project file.

Configure the connection

With the Codex CLI installed, run:

codex mcp add every --url https://admin-mcp.every.ai/mcp
codex mcp login every

Follow the OAuth sign-in and consent flow in the browser. Confirm the correct account. To inspect the configured server list, run:

codex mcp list

Codex stores the user configuration in ~/.codex/config.toml. The equivalent server definition is:

[mcp_servers.every]
url = "https://admin-mcp.every.ai/mcp"

Use the CLI or your client’s MCP settings to avoid overwriting unrelated configuration. Official Codex guidance also supports project-scoped .codex/config.toml in trusted projects. Local clients on the same host can share configuration, but a hosted ChatGPT chat does not inherit your local file.

Check setup and live access

Start or restart the client session as its connection settings require. In the CLI conversation, /mcp shows the active servers. Server registration is not enough: verify an actual tool result.

If Every reports incomplete signup, ask Codex to follow get_signup_status. Confirm an organization name and any optional details you want to provide. Then use complete_signup with only confirmed values. Treat profile suggestions as unverified candidates.

A safe first business request is:

Use Every to read a small sample of People, Companies, or open deals.
Return the actual records this connection can access.
Do not create, edit, send, or dismiss anything.
If signup is incomplete, explain the required step.
If a tool fails, report that failure instead of inferring a result.

Compare the returned record with your workspace. Your completed result is an authorized connection plus a verifiable read, not merely a successful configuration command.

Frequently asked questions

Can I use Codex to create invoices?

Use the available account tools after you verify access. Review recipient identity, scope, currency, and totals. Important external sends require confirmation or an explicit send instruction.

Can I access free guest tools through this server?

The MCP server works on your authenticated workspace. Guest document tools exist inside compatible every.ai browser pages. See Every’s agent paths rather than sending guest tool calls to the hosted server.

Does a local connection work in ChatGPT web?

Local configuration does not grant a hosted chat access. Use the Every ChatGPT app for that surface.

Setup reviewed October 14, 2026. See OpenAI’s MCP configuration guide, OpenAI’s MCP command reference, and Every’s current setup reference.

Start turning your network into new business.

Connect your inbox and LinkedIn, and Every builds your CRM and starts finding warm leads.