Why an agent needs an email identity#
Many useful workflows still begin or end with email: supplier quotes, customer replies, verification messages, support requests and operational notifications. Giving an agent a dedicated address keeps that communication separate from a human inbox.
The programmable inbox pattern#
Instead of automating a personal Gmail account, create a mailbox specifically for the agent. The application can receive messages, search them, read the relevant content and send or reply through an API or MCP tools.
Hosted inbox or custom domain#
A hosted address is useful when speed matters. A custom address such as purchasing@yourcompany.com is useful when the agent represents a business or workflow externally.
Connect through MCP#
For an MCP-compatible agent, email becomes a set of tools: list mailboxes, search email, read a message, send, reply, mark read, delete and restore.
Connect through REST#
Applications that do not use MCP can call the same email workflow through REST endpoints and Bearer-token authentication.
Keep the identity separate from the agent#
The useful abstraction is not another webmail client. It is an email identity that software can operate. That lets you change the agent or application without changing the address people and systems already use.
Start with one workflow#
Create one inbox for one agent and give it a narrow job. A supplier inbox, lead-response inbox or verification inbox is easier to reason about than routing every business email through one autonomous system.