Model Context Protocol (MCP) lets you expose arbitrary tools to Claude sessions. Emails4Agents ships a built-in MCP server — wire it to your Claude Code config and email becomes a first-class tool call.
Connect to Claude Code
Add to ~/.claude/settings.json:
{
"mcpServers": {
"emails4agents": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://api.emails4agents.com/mcp/sse",
"--header", "X-API-Key:${E4A_API_KEY}"
],
"env": {
"E4A_API_KEY": "e4a_your_key_here"
}
}
}
}
Restart Claude Code. You’ll now have these tools available in every session.
Available tools
| Tool | What it does |
|---|---|
list_domains | List all configured email domains |
create_domain | Add a new domain with auto DNS |
verify_domain | Check DNS propagation status |
list_inboxes | List inboxes, filter by domain |
create_inbox | Provision a new inbox |
send_email | Send from an inbox |
read_messages | Get messages from an inbox |
get_thread | Full conversation thread |
reply_to_message | Reply in-thread |
search_messages | Full-text search |
Example session
User: I need to send follow-up emails to everyone who replied to our
outreach campaign last week
Claude: Let me check the outreach inbox for replies.
[calls read_messages on [email protected], direction=inbound, date>=7d ago]
Found 12 replies. Sending follow-ups now...
[calls send_email 12 times with personalized follow-up content]
Done. Sent 12 follow-ups. 2 of the replies had negative sentiment —
I skipped those to avoid escalation.
Why this matters
Before MCP, giving Claude email capabilities meant either:
- Writing a custom tool integration in your system prompt
- Building an agent harness with email client libraries
- Paying for a third-party email tool connector
With the Emails4Agents MCP server, Claude gets email as a native tool the same way it gets bash or read_file. No additional code required.
The MCP server is included in the Emails4Agents API container — no separate deployment needed.