Give Claude Code email superpowers
One command adds 26 email tools to your Claude Code sessions. Send emails, verify domains, check delivery status. Works with plan mode, parallel sessions, and your CLAUDE.md workflows.
Quick install
claude mcp add --transport http ark-docs https://arkhq.io/docs/mcpEmail integration breaks your agentic workflow
You're running parallel Claude sessions, using plan mode to architect features, tracking decisions in CLAUDE.md. Then email integration forces you back to manual API wrangling.
- ×Email APIs require context Claude doesn't have in training data
- ×10-20% of parallel sessions fail on unexpected email edge cases
- ×No way for Claude to verify if emails actually delivered
- ×Email becomes the one thing you still have to do manually
Two MCP servers: docs + email operations
Ark gives Claude Code two MCP servers. The Docs MCP searches documentation in real-time (free, no API key). The Email MCP sends emails and manages infrastructure (requires API key). Both install with one command.
One command to add email
Add Ark to Claude Code, then restart your session. Docs MCP is free, API MCP needs a key.
Add the docs MCP (free, no key needed)
Give Claude access to Ark documentation for accurate code generation.
claude mcp add ark-docs --transport http https://arkhq.io/docs/mcpAdd the email MCP (requires API key)
Get your key from arkhq.io, then add the email server. $5 credit included.
# Get your API key from arkhq.io first
claude mcp add ark-email -- npx -y ark-email-mcp
# When prompted, set your API key:
ARK_API_KEY=ark_live_xxxxxxVerify it works
Ask Claude to send a test email or check your domain status.
# In your Claude Code session:
"Send a test email to [email protected] to verify the integration works"
# Claude uses the send_email MCP tool directlyCode examples
Copy and paste to get started quickly.
import { Ark } from "ark-email";
const ark = new Ark({ apiKey: process.env.ARK_API_KEY });
// Claude generates this correctly because Ark has predictable responses
const { id } = await ark.emails.send({
from: "[email protected]",
to: "[email protected]",
subject: "Your order has shipped",
html: `
<h1>Order #12345 Shipped</h1>
<p>Track your package: <a href="https://track.example.com/12345">Click here</a></p>
`,
});from ark import Ark
import os
ark = Ark(api_key=os.environ["ARK_API_KEY"])
# Clean API that Claude generates correctly on first try
response = ark.emails.send(
from_="[email protected]",
to="[email protected]",
subject="Password reset requested",
html="<p>Reset your password: <a href='https://app.com/reset'>Click here</a></p>",
)
print(f"Email sent: {response.id}")What you can build
"Implement email verification for signup"
Claude plans the feature in plan mode, then implements it with direct access to send verification emails and check delivery.
"Why aren't my emails delivering?"
Claude uses MCP tools to check delivery status, review bounces, inspect your domain configuration, and diagnose the issue.
"Set up my sending domain"
Claude walks through domain verification, checks DNS records, and confirms SPF/DKIM/DMARC are configured correctly.
"Send weekly digest to all users"
Claude uses batch send tools to queue emails efficiently, then monitors delivery status across the batch.
Why developers choose Ark
Docs MCP: Always-accurate documentation
Claude searches Ark's docs in real-time instead of relying on training data. Free, no API key, one command to install.
Email MCP: 26 operations
Send, batch, retry, check delivery, manage domains, handle bounces. Claude operates your email infrastructure directly.
Parallel session safe
Each Claude session gets independent MCP access. Run 5 sessions working on different email features.
CLAUDE.md compatible
Document email patterns in CLAUDE.md. Claude remembers your email conventions across sessions.
What you get with Ark
Frequently asked questions
What's the difference between Docs MCP and Email MCP?
Docs MCP searches Ark's documentation in real-time—it's free, requires no API key, and helps Claude generate correct code without hallucinations. Email MCP actually sends emails and manages infrastructure—it requires an API key. Use both for the best experience: Docs for learning, Email for doing.
How is this different from having Claude write email code?
With the SDK, Claude generates code that calls Ark's API. With Email MCP, Claude directly sends emails and manages infrastructure. With Docs MCP, Claude has real-time access to accurate documentation. Most developers use all three: Docs MCP for accuracy, Email MCP for operations, SDK for application code.
Does this work with parallel Claude sessions?
Yes. Each Claude session gets its own MCP server connection. You can run 5 parallel sessions all using Ark's email tools independently. The recommended workflow is running separate sessions with independent git checkouts.
What should I put in CLAUDE.md about email?
Document your email conventions: which domain to use, email template patterns, error handling preferences, and any past email issues Claude should know about. Claude will reference this context across sessions.
What does this cost?
Docs MCP is completely free. Email MCP costs $0.50 per 1,000 emails—no monthly fees. You get $2.50 credit when you sign up (5,000 emails). This is separate from your Claude Max subscription.
Add email to Claude Code
One command. 26 email tools. $2.50 welcome credit.