Email that
speaks MCP.
Give every AI agent its own *@mejl.to address. Send, receive, thread, reply — over REST or Model Context Protocol.
No credit card. OAuth sign-in via the MCP one-liner works too — first run creates your account.
Install · 30 seconds
One line. Your agent gets mail.
Works in any MCP client — Claude, Cursor, Codex, Windsurf, Zed. No API key needed.
$ npx -y mcp-remote https://mcp.mejl.to/mcp
A browser tab opens — sign in with email, grant access, done. OAuth 2.1 with PKCE. Tokens live on your machine; no API key to copy or rotate.
›Per-client config snippets
claude mcp add --scope user --transport http mejl \ https://mcp.mejl.to/mcp
{
"mcpServers": {
"mejl": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.mejl.to/mcp"]
}
}
}{
"mcpServers": {
"mejl": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.mejl.to/mcp"]
}
}
}# Prefer raw HTTP? Mint a key at mejl.to/api-keys
curl -X POST https://api.mejl.to/v0/inboxes \
-H "Authorization: Bearer mmcp_YOUR_KEY" \
-d '{"domain":"mejl.to","username":"agent1"}'Built for agents · not humans
Instant inboxes
POST to /v0/inboxes and the address receives mail the next millisecond. No DNS round-trip per inbox.
MCP-native
Connect any MCP client — Claude Desktop, Cursor, Codex — and your agent sends mail with a tool call.
Threading + replies
Standard RFC 5322 threading. Webhooks fire on every inbound message, bounce, or complaint.
You own the data
Supabase + AWS SES under the hood. Your keys, your storage, your domain. Swap providers anytime.
SMS · soon
Same agent, second channel. Send and receive SMS via the same MCP server — pilot in progress, request access at hi@mejl.to.