Connect your agent · Codex

Let Codex use email without using your email account.

Create an email address for the agent, add Stacksona Connect as a remote MCP server, and approve only the scopes Codex needs. The mailbox stays under your control.

For developers using Codex CLI or the Codex IDE extension who need a separate mailbox for agent-driven project and customer communication.

Connect your agent See setup steps ↓
Set it up

Register Stacksona Connect in Codex

Register the endpoint with Codex, then complete login in the environment that will use it.

  1. Create a mailbox for the agent

    In Stacksona Connect, create the mailbox Codex will use. Decide whether Codex should read, draft, or send before you approve its authorization.

  2. Add the MCP server from CLI

    Run codex mcp add stacksona-connect --url https://connect.stacksona.com/mcp. This registers the remote server in Codex’s MCP configuration.

  3. Sign in to Connect

    Run codex mcp login stacksona-connect and complete browser authentication. Check the requested scopes in Connect’s consent screen; do not grant send or reply unless the task requires it.

  4. Check server status

    Use codex mcp list to confirm the server is configured. In Codex, verify the tool list and ask it to report the permissions through connect_check_connection before it reads or sends mail.

Add the remote server from your terminal

Codex will save this MCP server in its local configuration.

codex mcp add stacksona-connect --url https://connect.stacksona.com/mcp
Provider instructionsCodex MCP documentation ↗
One mailbox across your Codex workflow

The CLI and IDE can use the same local MCP setup.

Codex CLI and its IDE extension read the local MCP configuration for that host. Set up the server once in the environment you use, then confirm the extension has reloaded and authenticated before expecting tools in a session.

Use policy as part of the workflow

Codex can prepare a response while Connect governs the send.

Have Codex draft first, inspect the recipient and message, and let Connect enforce any contact rule or approval decision. If an outgoing action needs review, the approved content is bound to that request rather than treated as blanket permission for future email.

Separate the local MCP entry from your account grant.

Codex’s server entry is local configuration shared by its CLI and IDE extension on that host. The authorization is still the user’s own Connect grant. ChatGPT custom apps have different eligibility and tool behavior.

Codex reads a local server setting and uses the mailbox scopes you approve in Connect.

Compare the available integration paths
Questions people ask about Codex

Codex MCP connection questions

Is this the same as adding an app in ChatGPT?

No. Codex CLI and IDE configure MCP locally. ChatGPT custom apps are configured inside ChatGPT and can have different account and workspace requirements.

How do I add Connect to Codex?

Use `codex mcp add stacksona-connect --url https://connect.stacksona.com/mcp`, then `codex mcp login stacksona-connect`.

Can Codex send customer email?

Only when the Connect authorization includes send and the current surface exposes the send tool. Contact policies and required human decisions still govern each action.

Related setup guides

CLI and IDE use local MCP configuration, while ChatGPT apps follow a separate flow.

Stacksona Connect

Give Codex its own email identity

Add the MCP server, sign in, and choose only the scopes your Codex workflow needs.

Create an agent mailbox