AI Agents Are Building Apps Now — Why Your Email API Better Speak Their Language
July 23, 2026 · Ferry Setyawan · 6 min read
The AI agent is the new developer.
Claude Code spins up a SaaS backend in 20 minutes. Cursor ships features while you sleep. OpenAI Codex writes PRs. Hermes runs cron jobs autonomously.
These agents don't read marketing pages. They read API docs. They parse OpenAPI specs. They grep package.json for dependencies.
And increasingly — they read MCP.
The protocol AI agents actually use
MCP (Model Context Protocol) is how AI agents discover tools. Instead of hardcoding API integrations, an agent queries an MCP server, gets a list of available tools, and calls them.
No SDK install. No reading docs. No copy-pasting API keys into env files.
The agent just... uses the service.
This is already happening for databases (Postgres MCP), file systems, browsers, and GitHub. But email? Email is still stuck in 2015.
The email API gap
Every transactional email API works the same way:
- Sign up on a website
- Read docs
- Install an SDK
- Copy API key
- Write code
- Test
- Deploy
An AI agent can do steps 3-7. But steps 1-2 require a human to navigate a marketing site, sign up, and read docs.
That's the gap.
MailAnvil: MCP-native email
MailAnvil is the first transactional email API with MCP discovery built in.
An AI agent building your app doesn't need you to tell it "use MailAnvil for email." It discovers MailAnvil through MCP, sets up the integration, and starts sending — all without you touching a dashboard.
How it works:
// Agent queries MCP
{
"method": "tools/list"
}
// MailAnvil responds with available tools
{
"tools": [
{ "name": "send_email", "description": "Send transactional email" },
{ "name": "verify_domain", "description": "Verify sending domain" },
{ "name": "get_stats", "description": "Get delivery statistics" }
]
}
// Agent sends email — no SDK required
{
"method": "tools/call",
"params": {
"name": "send_email",
"arguments": {
"to": "[email protected]",
"subject": "Welcome!",
"html": "<h1>Hello</h1>"
}
}
}
The agent never visited mailanvil.com. Never read docs. Never installed an npm package.
It just worked.
Why this matters now
AI agents are building more code every day. GH Copilot has 1.8M+ paying users. Claude Code is growing fast. AI-written PRs are becoming standard.
But every app needs email. Password resets, welcome emails, notifications, invoices — email is infrastructure, not a feature.
If your AI agent hits a wall at "add email," you have to step in. Log into Resend. Copy an API key. Install an SDK. Write boilerplate.
MailAnvil removes that wall.
The Indonesia angle
We built MailAnvil for Indonesian developers because:
- IDR pricing — no forex surprises. 20.000 emails for Rp 75.000/month.
- QRIS & GoPay — pay with what you actually use, not a credit card you don't have.
- Bahasa Indonesia docs — built for the dev who learned to code in Indonesian, not English.
- Cloudflare Workers native — deploy edge-first, latensi rendah untuk pengguna Indonesia.
MCP-native means the AI agent that builds your warung-online app, your UMKM dashboard, or your event platform just handles email automatically.
Getting started
For humans:
npm install @mailanvil/sdk
For AI agents:
{
"mcpServers": {
"mailanvil": {
"command": "npx",
"args": ["-y", "@mailanvil/mcp"]
}
}
}
That's it. The agent discovers MailAnvil, configures your domain, and starts sending.
No website visit required.
MailAnvil is the first MCP-native transactional email API. Built for Indonesian developers, Cloudflare Workers, and AI agents. Start free →
Tags: mcp, ai-agents, email-api, indonesia, cloudflare-workers, developer-tools