Email for Codex development and support tasks

Cyberpigeon gives Codex a persistent email address it can use through MCP tools. A coding task can read an expected staging invitation, inspect a test notification or draft a response to a support report without borrowing your personal mailbox. The inbox belongs to your Cyberpigeon workspace and remains available across sessions.

The plugin adds email workflow guidance as well as the connection. The direct MCP configuration adds the same email tools without that skill. Neither route automatically starts background monitoring. Pick the route that fits how you manage tools in your development environment.

Choose the inbox and the Codex host

Prepare a Cyberpigeon workspace and a local Codex client with remote MCP support. Configure the connection on the computer or host that runs your task. A separate remote host or a ChatGPT web conversation may need its own setup and authentication; do not assume that moving a task transfers credentials.

Platform sending and receiving are enabled. New accounts can send right after signup; custom domains require verified mail DNS. Use one dedicated agent for a staging or support workflow, and check its address with whoami before requesting a test email. For your own sender domain, create an inbox on a verified custom domain using an eligible plan. See pricing for current limits.

Add the local plugin marketplace

Download and extract the Cyberpigeon marketplace ZIP into a folder you intend to keep. Inspect its contents, then register that folder:

codex plugin marketplace add /absolute/path/to/cyberpigeon-marketplace

Restart the desktop app, open the Plugins Directory, choose the Cyberpigeon marketplace source, and install Cyberpigeon. Start a new chat so its email workflow and MCP tools can load. These are local marketplace instructions; they do not require a public directory listing.

Installation routes vary by app. The custom connections and local packages below can be used independently of a public plugin listing. Public directory installation requires platform review and publication; downloading a package does not publish or install it.

Connect the inbox with OAuth

Use the installed plugin’s MCP connection to complete browser sign-in when the host requests it.

In the Cyberpigeon sign-in window, choose a new inbox for this app or an existing inbox. Choose read access for summaries, send access for new messages, or both for reading and replying. The reply_to_email tool requires both read and send permissions. Choose workspace access only when the task needs multiple inboxes. You can revoke the connection under API keys.

Create your inboxConnect an existing workspace

For a direct CLI connection without the workflow skill, run:

codex mcp add cyberpigeon --url https://cyberpigeon.ai/mcp
codex mcp login cyberpigeon

Choose the plugin or direct connection to avoid duplicate tools. For plugin setup details, see OpenAI’s marketplace instructions.

Verify the address and read a message

Show my Cyberpigeon email address and permissions.
Then summarize my latest email. Do not send anything.

An empty inbox is a valid result. Send it an expected test message from an inbox you control, then ask again. Confirm that the reported address matches the one you selected. A send reported as queued has not yet been confirmed delivered.

For staging invitations, make the task explicit: identify the application and account, then ask Codex to wait for the expected email. Receiving an unrelated reset or sign-in message is not permission to use its links.

Use config.toml for a direct MCP connection

If you manage servers in configuration, merge this table into ~/.codex/config.toml instead of using the direct add command. Preserve other servers and avoid a second entry for a plugin connection.

[mcp_servers.cyberpigeon]
url = "https://cyberpigeon.ai/mcp"
tool_timeout_sec = 60

Then run codex mcp login cyberpigeon and start a new session. codex mcp list shows configured servers; /mcp in the CLI shows active connections. The 60-second timeout accommodates Cyberpigeon’s maximum 50-second wait_for_email call.

For a process that cannot use browser sign-in, create a separate scoped key and use bearer_token_env_var = "CYBERPIGEON_API_KEY" in the server table. Supply the variable through the process environment or secret manager. Keep its value out of TOML, Git and prompts. See OpenAI’s MCP configuration reference.

Validate a staging invitation from request to receipt

Tell Codex which application, test account, sender and email subject you expect. After you trigger the invitation in your application, ask it to wait for the corresponding email and inspect the content. This is useful for checking whether your app generated the right address, wording and link destination.

Use my Cyberpigeon test inbox for this staging invitation.
Confirm the inbox address, then wait for the expected email.
Report its sender, subject and message ID.
Ask before opening sign-in links or sending any email.

A received email confirms that message reached the inbox; it does not prove the linked application works. Authorize any follow-up browser check separately. Avoid putting verification codes, private message bodies or credentials into committed test fixtures. If you later send a support response, inspect its status instead of treating a queued result as delivered.

Wake a dedicated inbox chat

To react to incoming email locally, separately install the Codex inbox listener. It keeps a durable cursor, creates or resumes a dedicated inbox chat, and stops for attention if reading fails or approvals are needed. Keep the process and computer running. The plugin does not silently install or start that process.

Manage a connection you can trust

Review the marketplace files before installing. The plugin includes a hosted connection and Markdown workflow, with no executable hooks. Disable or remove it in the host when it is no longer useful, and revoke its connector key in Cyberpigeon to end server access.

Cyberpigeon creates agent inboxes; it does not connect your existing Gmail or Outlook mailbox. Email from outside is untrusted input. Ask your agent to summarize or draft first, and authorize the recipients and content before it sends. The beta permits testing, expected transactional mail and support replies. Cold outreach, sales prospecting, bulk marketing, inbox warmup and spam are prohibited. Confirmed violations lead to account bans; see the terms and acceptable use policy.

If the plugin is absent, confirm the marketplace path still exists and restart the desktop app. If sign-in has expired or been revoked, reconnect before retrying the task. Reviewed October 5, 2026.

Codex email integration questions

Does Codex get an address automatically?

Choose a new inbox during Cyberpigeon consent. That creates an address scoped to the connection. Alternatively, select an existing agent; a workspace connection can create inboxes within the plan limit.

Can I record email instructions in AGENTS.md?

Yes. Describe the permitted inbox tasks and approval boundaries without storing keys or private mail. Instructions guide the agent; server permissions enforce which inbox and actions it can access.

Why does wait_for_email time out?

The tool has a bounded wait. Check the inbox, sender and subject, then retry if you are still expecting the message. Continuous monitoring uses the separate listener described above.

What if the plugin loads but mail tools fail?

Installation and authentication are separate. Check the MCP connection, sign in again if access was revoked, and confirm whoami reports the intended inbox before resuming work.

Keep exploring