Provisions inboxes, lists and opens messages in full, and sends email from any address on the account.
5actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Lyro sends an email through AgentMail to reach customers outside of chat. Support agents offer assistance across multiple channels from a single interface.
Lyro creates a new AgentMail inbox to organize incoming messages by department or topic. Teams manage separate email flows without mixing unrelated conversations.
Lyro retrieves all messages from an AgentMail inbox so Lyro can respond to queued customer requests. Agents see their full inbox history in one call.
Each card is one request a support team gets, and the Agent mail actions Lyro runs to close it.
Lyro lists the inboxes on the account, pulls the messages in one of them and opens a single message with its body, attachments, labels and metadata, so the reply answers the message rather than the subject line.
Lyro provisions a new AgentMail inbox when a workflow needs its own address and sends from it, so automated mail does not go out through a shared human mailbox.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Agent mail actions it has and picks the ones a request needs.
Authorize the Agent mail account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Lyro maps it to the Agent mail actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeAgent mail · Lyro
What can you do in Agent mail without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Lyro can do inside Agent mail.
Lyro already answers customers over email on your existing help desk. An AgentMail inbox is a separate address it owns outright, created with Create Inbox and sent from with Send Email, which fits agent-to-service correspondence such as vendor forms or automated replies that should not enter your support queue.
All 5 actions your agent can call on Agent mail, straight from the live MCP connection.
Create a new AgentMail inbox via API.
Retrieve the complete details of a specific email message from an AgentMail inbox.
List all inboxes available to the authenticated AgentMail account.
List messages from an AgentMail inbox.
Send an email using AgentMail API.
Same connection, same setup. Pick the next one your team already uses.
Posts messages and files into rooms, reads history and unread counts, opens and closes assigned tasks, and sets up rooms, members and invite links.
Replies in channel and spins up threads, reads recent and pinned messages for context, grants member roles, and applies moderation actions on a report.
Reads the message log behind a delivery question, checks domain verification and API quota, and provisions SMTP users, tokens, and event webhooks.
Reads back what happened on a call, places outbound callbacks, keeps voice agent knowledge bases current, and batch tests an agent before it ships.
Creates and updates contact records, finds the thread a customer means with its channel and status, and keeps inboxes, labels, and webhooks accurate.
Reads space history, posts and targets messages, manages team and space membership, and registers webhooks in Webex.

Authorize the account and your agent has all 5 actions from the first conversation.
