Send from your own Gmail
Every message goes out through the Gmail API from the account you connected — your address, your Sent folder, your sender reputation. Each recipient gets an individual, tracked copy.
Connect Claude, Cursor or any MCP client to Maildriply. Your assistant sends email from your own Gmail with open and click tracking, then reads back who opened, who clicked, and who needs a follow-up.
Works with Claude Code, Claude Desktop, Cursor, VS Code & more · free in early access
The MCP server uses the same send pipeline and tracking as the Maildriply dashboard — nothing is a separate, weaker path.
Every message goes out through the Gmail API from the account you connected — your address, your Sent folder, your sender reputation. Each recipient gets an individual, tracked copy.
Your assistant can see per-recipient delivery, opens, link clicks and unsubscribes, plus account-wide rates — and decide what to do next.
Replies land in the recipient's existing Gmail thread with a Re: subject. Target only the people who didn't open, or everyone the first email reached.
Claude Code, Claude Desktop, Cursor, VS Code and other clients that speak the Model Context Protocol over Streamable HTTP.
Create a key per device or tool. Make it read-only or allow sending. Revoke it from Settings and it stops working on the next request.
Daily sending quota, warm-up, suppression of unsubscribed recipients, and rate limits all apply. The AI can't change your sender address.
Sign in to the Maildriply dashboard, open Settings → AI & MCP, name your key and choose whether it may send. Copy it — it's shown once.
Claude Code:
claude mcp add --transport http maildriply https://api.maildriply.com/mcp \
--header "Authorization: Bearer mdk_your_key"Cursor and other clients with JSON config (Claude Desktop and VS Code steps are in the setup guide):
{
"mcpServers": {
"maildriply": {
"url": "https://api.maildriply.com/mcp",
"headers": { "Authorization": "Bearer mdk_your_key" }
}
}
}Try “Send a test email to myself” — it lands in your own inbox. Then ask your assistant to send for real and check back on opens and clicks.
Client-specific steps and the full tool reference are in the MCP setup guide.
send_emailSend now or schedule, to up to 500 recipientssend_follow_upReply in the original Gmail threadsend_test_emailPreview a message in your own inboxget_email_trackingPer-recipient opens, clicks and errorsget_recent_activityLive feed of opens, clicks, unsubscribesget_analytics_overviewOpen, click and delivery rateslist_emailsSearch sent and scheduled emailreschedule_emailMove or cancel scheduled sendslist_templatesReuse your saved templatesThe Model Context Protocol is an open standard that lets AI assistants call external tools. Maildriply runs a hosted MCP server, so an assistant like Claude or Cursor can send tracked email and read tracking data on your behalf.
MCP clients ask you to approve tool calls, and you choose what each key can do: a read-only key can look at emails and tracking but cannot send. Every send is recorded in your dashboard, and you can revoke a key instantly from Settings.
No. Maildriply only holds the gmail.send permission, which cannot read your mailbox. The assistant can see what you sent through Maildriply and the tracking events on it — never your inbox.
Always the Gmail account you connected in the dashboard. The sender address isn't something the assistant can set, which keeps every message aligned with your domain's SPF, DKIM and DMARC.
Today the server works with clients that let you add a remote MCP server with an Authorization header — Claude Code, Claude Desktop, Cursor, VS Code and similar. Sign-in-based connectors for web apps are on the roadmap.
Yes. MCP access is included while Maildriply is in early access. Sends count against the same daily quota as the dashboard.
Connect Gmail, create a key, and your AI assistant can send tracked email in two minutes. Free during early access.