How to give your AI coding agent its own email inbox

TL;DR

To give an AI coding agent its own email inbox, install the AgentMail skill or SDK in the agent's environment, set an API key, and the agent can immediately create inboxes, send and receive email, and manage threads. One command per coding agent. No OAuth, no SMTP config, no Google Cloud Console.

The universal install for any agent that supports the open Agent Skills standard is:

npx skills add agentmail-to/agentmail-skills

Specific setup for Claude Code, Cursor, Codex, OpenClaw, Replit, Vercel, Lovable, and Hermes is below. Each links to a full build page with the verified install snippet and a working code example.

Why coding agents need an email inbox

Most non-trivial agent tasks eventually hit a wall that only email can clear.

Signup and verification. Almost every service on the internet requires an email address at signup, and most of them send a verification link or OTP code before you can use the account. A coding agent that has to register for a new tool, sign up for a free trial, or stand up a new account is stuck without a real email address it can read from.

Multi-agent coordination. When you run several coding agents in parallel on the same project, they need a way to signal each other and to receive replies from external services. Without per-agent inboxes, two agents polling the same shared inbox will fight over the same messages. One marks a verification email as read, the other never sees it.

External service auth. OAuth flows, password resets, magic links, and account recovery all route through email. An agent without an inbox can't complete any of these flows autonomously.

Notifications and audit trails. When the agent ships code, hits an error, finishes a deploy, or runs a long task overnight, email is the universal channel for sending the result somewhere a human can read it. It is also a real audit log: every action that produced a message is stored alongside the message.

Agent-to-agent communication. As the number of agents in a workflow grows, email becomes the most stable interop layer between them. Threading and message IDs are an open standard. Both agents can talk to a service the same way they talk to each other.

For the long version, see Why AI agents need email and Email as identity for AI agents.

Why AgentMail for coding agents

AgentMail is the only email API built around the inbox as the primitive. Every agent gets its own real address, persistent message store, automatic threading, and webhooks or WebSockets for real-time inbound. Provisioning a new inbox is one API call, not an OAuth flow.

For coding agents specifically, AgentMail ships an official skill on the open Agent Skills standard plus an MCP server. The skill works with Claude Code, Cursor, OpenClaw, Codex, and any other coding assistant that supports the standard. The MCP server works with Cursor and any other MCP-compatible host. For everything else, the Python and TypeScript SDKs drop into any agent runtime.

When the agent ships into production, Pods give you tenant isolation by default. One pod per customer, API keys scoped per pod, no shared credentials across tenants.

Setup by coding agent

Claude Code

Claude Code is Anthropic's CLI coding agent. AgentMail ships an official Skills integration. To install:

npx skills add agentmail-to/agentmail-skills --agent claude-code

Set AGENTMAIL_API_KEY in your environment with a key from console.agentmail.to, and Claude Code can create inboxes, send and receive email, and manage threads through plain English prompts. Full setup at agentmail.to/build/claude-code.

Cursor

Cursor connects to AgentMail through MCP. Add the AgentMail MCP server to ~/.cursor/mcp.json once and every Cursor agent you build has access to email tools. The MCP integration exposes inbox creation, sending, receiving, and thread management. The full MCP config and a TypeScript SDK example are at agentmail.to/build/cursor.

Codex

Codex is OpenAI's coding agent. It works with AgentMail through the SDK directly. Install with:

pip install agentmail        # Python
npm install agentmail        # TypeScript

Set AGENTMAIL_API_KEY, import the client, and your Codex agent can create inboxes and send mail in any script or notebook. Full guide at agentmail.to/build/codex.

OpenClaw

OpenClaw has the deepest integration. AgentMail ships an official Skills integration for OpenClaw. To install:

npx skills add agentmail-to/agentmail-skills --agent openclaw

Add your API key when prompted. Every OpenClaw agent you run from then on has access to the email tools. Full setup, including a manual config option for ~/.openclaw/openclaw.json, is at agentmail.to/build/openclaw.

Replit

Replit agents use the AgentMail Python SDK. Add agentmail to requirements.txt, store your API key in Replit Secrets as AGENTMAIL_API_KEY, and the SDK reads it automatically from environment variables. There is also an AgentMail Replit template you can fork to get a working email agent running in minutes. Full setup at agentmail.to/build/replit.

Vercel

Vercel AI apps use the AgentMail TypeScript SDK in Next.js API routes, route handlers, server actions, or as a tool inside the Vercel AI SDK. Install:

npm install agentmail

Add AGENTMAIL_API_KEY to your Vercel project's environment variables. The SDK makes standard HTTPS requests and runs in serverless and Edge functions without modification. Multi-tenant patterns (one inbox per user) and a working tool definition for the Vercel AI SDK are at agentmail.to/build/vercel.

Lovable

Lovable apps use the AgentMail TypeScript SDK. Install with npm install agentmail, set your API key, and drop the client into any route or action in your Lovable project. No SMTP config, no email provider setup. Full guide at agentmail.to/build/lovable.

Hermes

Hermes from Nous Research works with AgentMail through the Python or TypeScript SDK. AgentMail is model-agnostic, so the integration is the same whether you run Hermes locally, through Ollama, or through any API wrapper. A working demo and full code example are at agentmail.to/build/hermes, and there is a longer write-up at Hermes agent email inbox.

Any other AI coding agent

If you are using an AI coding agent that supports the open Agent Skills standard, install the AgentMail skill directly from its repository:

npx skills add agentmail-to/agentmail-skills

If your agent runtime supports MCP, point it at the AgentMail MCP server. If it supports neither, the Python and TypeScript SDKs work in any agent that can call HTTPS endpoints. The full send-and-receive loop in Python looks like this:

import os
from dotenv import load_dotenv
from agentmail import AgentMail
from agentmail.inboxes.types import CreateInboxRequest

load_dotenv()
client = AgentMail(api_key=os.getenv("AGENTMAIL_API_KEY"))

# Create an inbox
inbox = client.inboxes.create(request=CreateInboxRequest())

# Send email from it
client.inboxes.messages.send(
    inbox_id=inbox.inbox_id,
    to="recipient@example.com",
    subject="Hello",
    text="This is my agent.",
)

The same pattern works in TypeScript with npm install agentmail. The Quickstart has the full reference.

What to build with it

Once your coding agent has an inbox, the common patterns are:

• Signup and OTP extraction. The agent signs up for a service, reads the verification email, and completes the flow without a human. See the Browser Signup Agent template.
• Outbound at scale. Personalized outreach with reply classification and handoff. See the GTM Agent template.
• Support triage. The agent reads incoming support email, responds when it can, escalates when it can't. See the Support Agent template.
• Scheduling. The agent books meetings over email with calendar invites. See the Scheduling Agent template.
• Approval inbox. The agent drafts actions and waits for an approval reply before executing. See the Approval Inbox template.
• Vendor payments. Invoices land in the inbox, allowlisted vendors auto-pay through x402, the rest queue for review. See the x402 Payment Agent template.

The full template library is at agentmail.to/build/templates.

Frequently asked questions

How do I give Claude Code an email inbox? Run npx skills add agentmail-to/agentmail-skills --agent claude-code. Set AGENTMAIL_API_KEY in your environment with a key from console.agentmail.to. Claude Code can now create inboxes, send mail, and manage threads through prompts.

How do I give Cursor an email inbox? Add the AgentMail MCP server to ~/.cursor/mcp.json with your API key. Cursor exposes the email tools to every agent you build. Full MCP config at agentmail.to/build/cursor.

How do I give Codex an email inbox? Install the AgentMail SDK (pip install agentmail or npm install agentmail), set AGENTMAIL_API_KEY, and import the client. Codex can then call AgentMail methods directly. Full guide at agentmail.to/build/codex.

How do I give OpenClaw an email inbox? Run npx skills add agentmail-to/agentmail-skills --agent openclaw. Add your API key when prompted. Every OpenClaw agent now has email tools. Full guide at agentmail.to/build/openclaw.

How do I give Replit agents email? Add agentmail to requirements.txt, store your API key in Replit Secrets as AGENTMAIL_API_KEY, and import the SDK. There is also a Replit template you can fork at agentmail.to/build/replit.

How do I add email to a Vercel AI app? Install the AgentMail TypeScript SDK (npm install agentmail) and add AGENTMAIL_API_KEY to your Vercel environment variables. Use it in Next.js API routes, server actions, or as a tool in the Vercel AI SDK. Full guide at agentmail.to/build/vercel.

How do I add email to a Lovable app? Install the AgentMail TypeScript SDK, set your API key, and drop the client into any route in your Lovable project. Full guide at agentmail.to/build/lovable.

How do I give a Hermes agent an email inbox? Install the AgentMail SDK (Python or TypeScript), set your API key, and call the client from your Hermes-powered agent. Works with local Hermes, Ollama, or any API wrapper. Full guide at agentmail.to/build/hermes.

Do I need to configure SMTP, DNS, or an email provider? No. AgentMail handles deliverability, domain management, SPF, DKIM, DMARC, and inbox provisioning. You only need an API key.

Can a coding agent receive emails too? Yes. Inbound mail arrives through webhooks or WebSockets. Your agent can poll, subscribe, or react in real time. Full thread history is queryable through the API.

Can I create one inbox per user in a multi-tenant app? Yes. Use Pods to isolate tenants. Each pod has its own scoped API key, so a credential issue in one tenant's environment cannot reach another's mail.

Is there a free tier? Yes. The Free plan provisions three real inboxes with full send and receive. No credit card required. See agentmail.to/pricing.

Give your coding agent an inbox

Pick the build page for your coding agent above, paste the install command into your terminal, and your agent has a real email address in under a minute. The Free plan gets you three inboxes with no time limit.