
Wire your coding agent into real email so it can send updates, read replies, and search threads without custom SMTP code.
Overview
dev.primitive/email is a MCP server for the Build phase that lets AI agents send, receive, search, and reply to email over Model Context Protocol.
What is this MCP server?
- Send, receive, search, and reply to email over MCP from Claude Code, Cursor, or Codex
- Hosted streamable HTTP remote at primitive.dev—no local mail server to operate
- Version 0.1.0 registry entry with GitHub source in primitivedotdev/primitive-mono-repo
- Designed as email infrastructure for AI agents rather than a human-only inbox UI
- Composable with other MCP tools for support, onboarding, and lifecycle messaging
- Registry version 0.1.0
- 1 streamable-http remote: https://www.primitive.dev/mcp
- 4 email capabilities stated: send, receive, search, reply
What problem does it solve?
Agents that need real email today force you to build and maintain separate mail APIs, parsers, and auth flows instead of talking to one MCP integration.
Who is it for?
Indie builders adding agent-driven support, onboarding sequences, or inbox triage without owning full mail infrastructure.
Skip if: Teams that only need a static contact form or already run a hardened ESP pipeline with strict compliance you cannot route through a third-party MCP.
What do I get? / Deliverables
After you register the Primitive email remote, your agent can handle mailbox operations through standard MCP tools while you focus on product logic.
- MCP-configured agent that can invoke email send, receive, search, and reply tools
- Reduced custom mail-stack code in your agent or backend integration layer
Recommended MCP Servers
Journey fit
Email plumbing is added while you integrate external services into the product or agent stack, before you ship automated outreach or support flows. Integrations is where MCP bridges to third-party protocols; agent email fits alongside other outbound channels and webhooks.
How it compares
MCP email transport for agents, not a marketing automation skill or ESP dashboard.
Common Questions / FAQ
Who is dev.primitive/email for?
Solo and small-team builders using Claude Code, Cursor, or similar agents who want programmatic send/receive/search/reply without custom SMTP integrations.
When should I use dev.primitive/email?
Use it during Build when you integrate outbound and inbound email into an agent workflow, support bot, or automated lifecycle messaging.
How do I add dev.primitive/email to my agent?
Add the streamable HTTP remote https://www.primitive.dev/mcp in your MCP client config per Primitive’s docs, then restart the agent session.