AGENT IDENTITIES YOUR DIGITAL EMPLOYEE, CONNECTED
Agents come and go.
Identity endures.
Own the identity.
Your AI agent is your digital employee.
Give it an email address. Give it a phone number.
Access is coming soon.
MEET YOUR DIGITAL EMPLOYEE
One identity. An entire sales flow.
ALEX → YOUR DIGITAL EMPLOYEE
A question lands in its inbox.
Hi Sara. Could your team help us with setup?
Absolutely. Tell me what you’re working with and I’ll help you find the right next step.
Your agent uses the business information you provide. Mailrun carries the email and replies.
YOUR IDENTITY. YOUR CHOICE.
Switch agent providers.
An agent identity is the name and contact channels people use to reach your AI agent. Mailrun gives your digital employee its own email address and phone number, with API and MCP access controlled by your company.
Keep that identity in Mailrun when you change the agent or model behind it. Your team supplies the agent, its business knowledge, and the tools it uses.
sara@example.com
+1 (202) 555-0147
02 / GET CONNECTED
You bring the employee.
- 01 / YOUR EMPLOYEEYOUR AGENTYour instructions · Your choice
Bring your AI agent.
Choose the agent, its instructions, and its job. Mailrun does not supply the agent.
- 02 / ITS MAILRUN IDENTITYmailrun.EmailPhone
Give it an identity.
Connect email and phone through API or MCP. Your hosted voice agent handles live calls.
- 03 / YOUR BUSINESSREADY FOR REAL WORKKnowledge · Calendar · Permissions
Put your tools to work.
Add your business knowledge and calendar. Set permissions. We’ll help test the first conversation.
Give your agent reach.
Email caps, phone usage limits, and scoped access help keep your digital employee within bounds. Give it room to work, with guardrails built in.
See how you stay in control03 / MADE TO INTEGRATE
API when you build.
MCP where
you work.
Build directly against the HTTP API, or use MCP to bring email and phone tools into your agent’s working environment.
- Identity separate from the model
- Scoped access to communication
- Conversation history through the API
EMAIL · PHONE · API · MCP Two communication channels.
Two ways to integrate.
MODEL CONTEXT PROTOCOL
Bring communication
into the agent’s workspace.
Connect compatible agent clients to Mailrun’s email and phone capabilities through MCP.
Email and phone tools in your agent’s workspace.
Let’s talk through your client and workflow.
04 / THE PEOPLE BEHIND IT
mailrun.Technical depth.
A personal connection.
Talk directly to the people building it.
Get answers from the team responsible for the product, from your first integration onward. Bring your workflow and your questions. We’ll help you connect your agent and work through setup.
Talk with our teamA direct conversation about your integration.
LET’S BUILD SOMETHING USEFUL
Give your agent
an identity of its own.
Access is coming soon. Request Access and we’ll follow up when Agent Identities is ready for you.
A conversation with our team.
No account or subscription is created by this request.
What’s included at launch?
Email, phone, API, and MCP. Give your agent a dedicated email address and phone number, then connect through the HTTP API or MCP. We’ll work through setup and usage limits with you during onboarding.
What does my agent need to answer calls?
Inbound conversations require your running agent to expose a public HTTPS voice endpoint. A desktop or MCP connection alone cannot answer live calls. We’ll verify the voice connection with you during onboarding.
Does Mailrun run my agent?
Your application runs the agent and chooses what it does. Mailrun supplies the communication identity, email and phone channels, and API and MCP access. You control the model, workflow, and approval process.
How do I get started?
Request Access using the form below. While you wait, explore our quickstart and demos to see how your agent will connect. Read the quickstart →
Can I bring my own domain?
Yes. Tell us which domain you want your agent to use. We’ll confirm eligibility and help connect it during onboarding.