Devin + AgentMail

Give Devin its own email inbox

AgentMail is the fastest way to give a Devin agent its own email inbox. It can send email, receive replies, and manage full conversation threads from a dedicated inbox it owns.

Start for free Docs

[ Install ]

One command

Devin Desktop supports MCP natively. Connect AgentMail once and Devin can create inboxes, send email, and handle replies as part of any workflow.

[ Why email ]

Why your Devin agent needs its own inbox

Devin uses email natively

Once MCP is connected, Devin treats AgentMail tools like any other capability. No boilerplate - just describe what you want.

One inbox per workflow

Create a fresh inbox for each task: outreach, support, build notifications. Separate contexts, clean audit trails, isolated reputations.

Real inbound, not just sending

Every inbox is a real address with inbound webhooks and threading. Incoming email arrives within seconds and your agent can reply in-thread.

[ Code ]

Working code

[ FAQ ]

FAQ

Common questions about AgentMail and Devin.

Yes. Cognition renamed Windsurf to Devin Desktop on 2 June 2026. Your plan, pricing, extensions and settings carried over, and the editor stayed backwards-compatible with Windsurf and VS Code. The local agent Cascade was replaced by Devin Local, which is the default agent in new tabs.

Add the AgentMail MCP server to your Devin config with an x-api-key header, then ask Devin to create an inbox. Devin Local reads ~/.config/devin/mcp_config.json, or .devin/mcp_config.json per project. Once connected, Devin can create inboxes, send email, read replies and manage threads as native tools.

Devin Local reads ~/.config/devin/mcp_config.json (or %APPDATA%\devin\mcp_config.json on Windows), and .devin/mcp_config.json for per-project config. Use .devin/mcp_config.local.json for a personal API key - it is gitignored. The legacy Cascade agent reads ~/.codeium/windsurf/mcp_config.json instead.

Yes. Cascade uses the serverUrl form shown in the second config block. Cascade is legacy - Devin Local is the default agent for new tabs - so use the Devin Local config unless you are deliberately staying on Cascade.

Yes. Every AgentMail inbox is a real email address with inbound webhooks and full threading. Devin can read replies and respond in the same thread. Use webhooks or the API to trigger your agent when new mail arrives.

Yes, on the Developer plan and above. Point a custom domain at AgentMail and every inbox you create gets an address on it. The free plan uses AgentMail-provided addresses.

No. AgentMail handles sending, receiving, threading, storage and deliverability. You provide an API key - that is all. No SMTP, no OAuth, no Google Workspace seat.

Your API key is not reaching the server. The AgentMail MCP server completes the connection and lists all its tools before it validates your key, so a wrong, missing or unexpanded key looks like a successful connection until a tool actually runs - at which point you get "Forbidden (HTTP 403) - the authenticated credential lacks permission for this action". Check the x-api-key value in your config. If you used ${env:AGENTMAIL_API_KEY}, confirm that variable is set in the environment Devin was launched from, or put the literal key in .devin/mcp_config.local.json instead, which is gitignored.

Free: up to 100/day with no separate monthly cap. Developer ($20/mo): 100/5 min, 1,000/day, and 10,000/month. Startup ($200/mo): 1,500/5 min, 15,000/day, and 150,000/month. Enterprise: custom.