Send email
Resend
Email API for developers that sends and receives email from a verified domain over REST, SMTP or MCP.
At a glance
- Provider
- Resend
- Category
- Send email
- Type
- Hosted API
- Pricing model
- Monthly plans, $20 for 50,000 emails on Pro, overage per 1,0002
- Free tier
- 3,000 emails a month, 100 a day3
- Authentication
- API key; OAuth for the MCP server8
- Connect via
- REST API, SMTP, MCP server, SDKs, CLI8
- Read from the provider's pages
- 2026-11-04
Pricing
- Pricing model: Monthly plans with an included email volume, plus overage per 1,000 emails
- Free tier: 3,000 emails a month, capped at 100 a day; sent and received emails both count
- Card required for free tier: Not published
- Official MCP server: Yes, remote and local
- Address or package: Remote
https://mcp.resend.com/mcp; localnpx -y resend-mcp - Docs MCP server:
https://resend.com/docs/mcp(3 tools:search_resend,query_docs_filesystem_resend,submit_feedback; answered without auth)
- Who creates the account: A person creates the account; Stripe Projects can create one from a CLI command
- Who creates the account (other page): Stripe Projects: no signup form, an agent can run it
- Where to get a key: resend.com/api-keys, or approve OAuth in a browser
- REST API:
https://api.resend.com - MCP server:
https://mcp.resend.com/mcp - OpenAPI spec:
https://resend.com/openapi.json(alsohttps://resend.com/openapi.yaml; the GitHub copy is newer)
- API requests: 10 requests per second per team, shared across API keys
- Same on every plan: Upgrading does not change it
- Burst: No burst allowance
- Data location: United States, whichever sending region you pick
- Retention: 30 days on Free, Pro and Scale
- Used for training: No; neither Resend nor its subprocessors use customer content to train or fine-tune models
Read from Resend’s own pages on 2026-11-04. Every number links to the page a value came from. For agents, the same facts as markdown: /tools/send-email/resend.md