How MailAgent works
MailAgent is a Google Workspace Add-on for Gmail. It runs in your inbox 24/7. It can draft replies, send replies, and organize threads with labels.
You control what it touches. You also control how it writes. You can optionally give it tools via MCP to take real actions.
What MailAgent can do
Draft replies automatically in the right tone and format.
Respond for you (optional) instead of only drafting.
Apply Gmail labels to route and prioritize conversations.
Call external MCP tools to run research or execute business logic.
Feature docs
How it works (high-level flow)
MailAgent watches the Gmail labels you enable.
For each matching email, it builds context from the thread and your settings.
The agent decides what to do:
create a draft, or
send a reply, and/or
add/remove labels, and/or
call MCP tools for extra context or actions.
MailAgent writes the result back to Gmail (drafts, sent emails, and labels).
Configure MailAgent
Labels (scope control)
Use labels to define what the agent should handle.
Include labels: the agent only runs on these.
Exclude labels: add “do not touch” areas like
FinanceorLegal.
Draft vs respond mode
Draft mode: creates drafts only. You review and click Send.
Respond mode: sends replies on your behalf.
Start with Draft mode. Switch to Respond mode after you trust the behavior.
Prompt (your policy + voice)
Your prompt is the agent’s operating guide. Keep it explicit.
Include:
writing style (short, friendly, formal, etc.)
rules (what not to do)
escalation criteria (when to ask you instead of replying)
label rules (when to apply which label)
External MCP tools (optional)
Connect MCP servers to let the agent access your systems and workflows.
Common uses:
look up customers in your CRM
create or update support tickets
schedule meetings
run research and summarization
When tools are available, the agent can call them and use the results in its reply.
What you’ll see in Gmail
Drafts created in the thread (Draft mode).
Replies sent from your account (Respond mode).
Labels applied to threads for routing and follow-up.
Last updated