AgentMail
AgentMail gives AI agents their own email inboxes. Through this connector, an agent (or you, in Claude) can spin up a dedicated inbox on the fly, then send, receive, reply to, and forward email, with full thread context, drafts, and attachments, entirely through tool calls. Unlike traditional email APIs built for one-way notifications, AgentMail is built for two-way conversations: an agent can read an incoming thread, understand it, and respond in context, just like a person would. This makes email a first-class communication and identity channel for agents, letting them sign up for services, coordinate with people, and talk to other agents. Key capabilities exposed over MCP: • Inboxes: create, list, get, update, and delete agent inboxes • Messages: send, reply, forward, list, and update • Threads: list, read, label, and delete full conversation threads • Search: full-text search across threads and messages • Drafts: create, list, read, update, send (with scheduling), and delete • Attachments: retrieve attachments by ID, with text extraction for PDF/DOCX Connect in seconds via OAuth using your AgentMail console identity. No API key required in Claude. Sign up free at console.agentmail.to.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Primary Subcategory
- Email APIs & Programmable Inboxes
- Secondary Subcategories
- Email Clients & Inbox AssistantsTeam Chat & MessagingTeam Chat & MessagingVendor API & SDK Integration ConnectorsWork Email & Calendar
- Brand
- AgentMail
- Access
- Account required
- First tracked
- 2026-06-12
- Tool count
- 24
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is visible.
Claude Discoverability Score
Live · refreshed daily. Last refreshedAgentMail in Email APIs & Programmable Inboxes
#1of 2competitors
This is the score for the Integration’s Primary Category, Email APIs & Programmable Inboxes. Claude found AgentMail in connector search, but did not show it in the connector picker or invoke it in the measured contested Runs. That is why the score is 0.
How this score is measuredWhat we measure
One core score. Three important factors to discoverability.
- Sets the score
Picked
· 0/100 - Diagnostic
Found
· 33.6/100 - Diagnostic
Positioned
· 0/100
Competing in Claude Email APIs & Programmable Inboxes
View CategoryWhat does 0/100 mean?
0 is AgentMail's rounded picker appearance rate. It appeared in the connector picker, or Claude invoked it directly, in 0% of contested conversations. All three measures are important to discoverability: Picked determines the headline score, Found shows how often Claude found AgentMail in connector search, and Positioned shows where it appeared in the picker.
AgentMail is 10 points from Buried.
FoundDiagnostic
Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.
PickedMain score
How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.
PositionedDiagnostic
What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.
24 tools agents can invoke
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are AgentMail alternatives on Claude?
As of 2026-08-14, AgentMail competes with Resend in Claude Email APIs & Programmable Inboxes, ranked by public Discoverability Score.
Where does AgentMail rank in Email APIs & Programmable Inboxes on Claude?
As of 2026-08-14, AgentMail ranks #1 of 2 in Claude Email APIs & Programmable Inboxes with a Discoverability Score of 0/100 (Invisible).
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.