AgentMail
Connect AgentMail so agents can send, receive, and reply to email from their own inboxes.
The AgentMail MCP server gives agents email inboxes of their own. Agents can create an inbox, send and receive email at its address, reply in threads, and manage its calendar, without touching anyone's personal mailbox.
For use cases and example prompts, see AgentMail for AI coding agents.
What is AgentMail?
AgentMail is an email provider built for AI agents. Each inbox is a real email address, such as support-bot@agentmail.to or an address at your own domain, with threads, drafts, labels, attachments, and a calendar that fills itself from emailed invitations. With AgentID, an agent can also use its inbox as an identity to sign up for other apps.
What agents can do
Once you connect AgentMail, agents can:
- List, search, and create inboxes, and read an inbox's details and metadata
- Read threads, messages, and attachments, and search them across the organization
- Send, reply to, and forward email, with attachments uploaded from the session
- Create, update, and send drafts, and set labels on messages and threads
- Check an inbox's agenda, create and update calendar events, and accept or decline invitations
- Manage the allow and block lists that control who an inbox can email
- Sign an agent up for apps through AgentID and list the accounts it already has
Agents can send email to anyone from any inbox in the connected organization, and AgentMail counts those sends against your plan's daily limit. Anyone whose agents can use this connection can read and send from those inboxes, so choose the projects and sharing options accordingly. Tell agents when they should only read, or draft replies for you to approve.
Setup
Go to Workspace Settings → Connectors (or a project's Connectors page) and click Connect on the AgentMail card (or Connect another to add another connection).
Step 1: who the connection is for
Choose whether the connection belongs to you or to your team, which projects can use it, and whose agents can use it. AgentMail starts on Personal Account. See connection options for what each choice means. Then click Continue.
Step 2: how agents reach AgentMail
The second screen has two tabs: AgentMail account and Access token. Pick one.
AgentMail account
Click Continue to AgentMail and sign in at the AgentMail Console. If you belong to more than one AgentMail organization, the consent screen asks which one to connect. Approve access, and you land back on the Connectors page with AgentMail connected.
Agents then use that organization's inboxes. If you picked Workspace Service Account in step 1, everyone's agents use that access — so pick an organization whose inboxes you're happy to share.
Access token
Use this tab if you'd rather paste a key than sign in. In the AgentMail Console, open Settings → API Keys and create a key. Keys start with am_, and the Console shows each one only once. Paste it into the AgentMail API Key field and click Connect AgentMail.
An organization key gives agents every inbox. To limit agents to one pod or one inbox, create a scoped key in AgentMail instead and paste that.
Both methods connect to AgentMail's hosted MCP server, so there's nothing to install.
Reconnecting and disconnecting
If AgentMail stops accepting a connection you made with AgentMail account, the Connectors page shows a Reconnect needed badge on it, and agents run without AgentMail. Click Manage, then Reconnect AgentMail, and sign in again. For an Access token connection, click Manage and paste a new key.
Manage is also where you change a connection's project access and sharing options.
Disconnect removes the connection from Superconductor. For an AgentMail account connection, Superconductor also asks AgentMail to revoke its access. If that fails, follow the notice to remove access in AgentMail. For an Access token connection, delete the key in the AgentMail Console if you no longer need it elsewhere.
Troubleshooting
- Authentication fails: reconnect the account or replace the API key. Check that the key still exists in the AgentMail Console and that you still belong to the connected organization.
- A send is rejected: the organization has hit its daily sending limit, or it was created by an agent and hasn't been verified yet. Verify or claim it in the AgentMail Console, or raise the limit on your AgentMail plan.
- An agent can't create another inbox: your AgentMail plan caps the number of inboxes. Reuse an existing inbox or upgrade the plan.
- A pasted key can't reach an inbox: the key is scoped to a different pod or inbox. Paste an organization key, or a key scoped to the inbox agents need.
- Agents can't see AgentMail: check the connection's project and sharing options. Start a new session after connecting.
When to use it
Ask agents to use AgentMail when a task needs to send or receive email from an address of its own: outreach, support, notifications, or signing up for a service. For example:
Create an AgentMail inbox for release announcements and send the beta testers listed in this doc a summary of what shipped this week.Read everything that arrived in the support inbox today and draft a reply to each. Don't send anything until I've reviewed the drafts.Our agent needs a Firecrawl account. Sign it up with AgentID using the research inbox and tell me where to find the API key.