Add email capabilities to Warp's built-in AI agent through MCP. Send, read, and manage email directly from your terminal.
Warp is a modern, GPU-accelerated terminal with a built-in AI agent that supports MCP servers. By connecting MultiMail, Warp's AI agent can handle email operations alongside your command-line workflows — sending deployment notifications, reading support emails, or managing contacts without opening a browser.
MCP servers in Warp are configured in ~/.warp/mcp.json using the standard MCP JSON format. The setup is straightforward: add the MultiMail server config, and Warp's AI agent automatically picks up the email tools. Warp supports stdio transport, which is what MultiMail uses.
This integration is ideal for DevOps engineers and terminal-centric developers who want to manage email as part of their CLI workflow. Combine Warp's blocks, workflows, and collaborative features with MultiMail's email tools for a unified terminal experience.
Sign up at multimail.dev and create an API key from your dashboard. This key authenticates all MCP server requests.
In the MultiMail dashboard, create a mailbox for Warp's AI agent to use. Set oversight to gated_send so all outbound emails require your approval.
Create or edit the file at ~/.warp/mcp.json and add the MultiMail MCP server configuration.
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
}
}
}Restart Warp to load the new MCP configuration. Warp reads the mcp.json file on startup and connects to configured servers.
Open Warp's AI agent panel and ask it to list your mailboxes. If configured correctly, you'll see your MultiMail mailboxes returned in the agent's response.
| Tool | Description | Example |
|---|---|---|
| send_email | Send an email from your agent mailbox to any recipient. | Send a deployment completion email after running your deploy script. |
| reply_email | Reply to a received email, maintaining the thread context. | Reply to an incident report email with the CLI commands you ran to fix it. |
| check_inbox | Check a mailbox for new or unread messages. | Check for new alerts or notifications between terminal tasks. |
| read_email | Read the full content of a specific email including headers and body. | Read a server alert email to understand what triggered the notification. |
| create_mailbox | Create a new agent mailbox on your MultiMail account. | Create a mailbox for infrastructure alerts and notifications. |
| list_mailboxes | List all mailboxes on your MultiMail account. | View available mailboxes to select the right sender for ops emails. |
| get_thread | Retrieve an entire email thread to see the full conversation history. | Review the full incident response thread before sending a resolution. |
| search_contacts | Search your contact list by name, email, or tags. | Find the on-call engineer's email to send them server logs. |
| add_contact | Add a new contact to your MultiMail contact list. | Add a new team member's email for future notifications. |
| tag_email | Tag or categorize an email for organization and filtering. | Tag incident emails with severity levels for post-mortem reviews. |
| list_pending | List all emails currently awaiting human approval. | Review queued notification emails before approving them. |
| decide_email | Approve or reject a pending email in the oversight queue. | Approve an incident resolution email after verifying the fix. |
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
}
}
}Add this to ~/.warp/mcp.json to connect MultiMail to Warp.
I just deployed the latest changes to production using 'git push production main'. Send an email to [email protected] with the subject 'Production Deployment Complete' listing the last 5 commit messages.Ask Warp's AI to send a deployment notification after running commands.
I ran 'kubectl get pods' and several pods are in CrashLoopBackOff. Check my MultiMail inbox for related alert emails, then send an incident report to [email protected] with the pod status and any relevant alert details.Use Warp's AI to compose an incident email based on terminal output.
{
"mcpServers": {
"multimail": {
"command": "npx",
"args": ["-y", "@multimail/mcp-server"],
"env": {
"MULTIMAIL_API_KEY": "mm_live_your_key_here"
}
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"]
}
}
}Combine MultiMail with other MCP servers in Warp.
Create Warp Workflows that include email steps. For example, build a deployment workflow that runs your deploy commands, then asks the AI agent to email the team a summary. Workflows make complex multi-step processes repeatable.
Warp's Blocks feature groups command output into logical units. Reference specific block output when asking the AI to compose emails. For example, 'send the output from the last test run block to [email protected]'.
Warp's AI agent can check your inbox, summarize emails, and help you respond without switching to a browser. This is especially useful during on-call rotations or when monitoring deployments, keeping all your operational context in one terminal.
Warp is currently available on macOS and Linux. If you need a terminal with MCP support on Windows, consider using Claude Code (Anthropic's CLI) which supports MCP servers and runs on all platforms.
Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a 38-tool MCP server. Formally verified in Lean 4.