Built for developers who live in the IDE
Email infrastructure your AI can operate.
Model Context Protocol (MCP) turns Hatched Send into a set of tools your agent can call — same capabilities as the dashboard and API, without leaving Cursor, Claude Desktop, or VS Code.
What MCP actually is
MCP is an open protocol so AI clients can discover and call tools on external products. Hatched Send exposes email ops as tools: create a template, enrol contacts, build a drip, check usage. The agent plans; Hatched Send executes against your tenant.
You're not pasting prompts into a browser builder. You're pairing an IDE you already use with a real ESP — BYOD database, your domain, fair send pricing.
Two ways to connect
Stdio or Hosted HTTP
Included · all plans
Local MCP (stdio)
Create an API key, paste the config into Cursor (or any MCP IDE). Your IDE runs npx against a package hosted on Hatched Send — no npm account, no repo clone.
- ·Free with any API key
- ·Key stays in your IDE config
Add-on · $19/mo
Hosted HTTP MCP
A managed endpoint for remote clients and teams that want MCP without a local process — enable under Billing / MCP.
- ·Same tool surface as stdio
- ·Great for cloud agents & shared setups
Cursor config
Drop this in and go
Create a key in Settings → API Keys (the UI copies this for you). Paste into ~/.cursor/mcp.json. Restart Cursor — npx installs the client from Hatched Send; your key authenticates every tool call.
{
"mcpServers": {
"send": {
"command": "npx",
"args": ["-y", "--package", "https://send.hatched.digital/mcp/send-mcp.tgz", "send-mcp"],
"env": {
"HATCHED_API_KEY": "sk_live_…",
"HATCHED_API_URL": "https://send.hatched.digital"
}
}
}
}Tool surface
What agents can do (safely)
Campaigns never send without explicit confirmation. Destructive deletes also require a human yes.
Templates & brand
- create_template_draft / save_template (MJML → HTML)
- list_templates, get_brand_context, update_brand
Audiences & contacts
- list_audiences, create_audience, add_subscriber
- list_subscribers with filters
Campaigns & analytics
- create_campaign → send_campaign (after you confirm)
- get_analytics, get_campaign_analytics, get_usage
Automations & infra
- create_automation, list_automation_triggers
- add_domain, verify_domain, connect_database, connect_r2
A workflow developers recognise
- get_account / get_brand_context — see plan, domain, and brand tokens
- create_template_draft → save_template — MJML in the IDE, compiled HTML in Hatched Send
- create_audience / add_subscriber — or sync Shopify and let Automations fire
- create_campaign → send_campaign — only after you confirm in chat
- create_automation — welcome drips with wait + send steps
Prefer raw HTTP? The same operations exist on our REST API — MCP is the ergonomic layer for agents.
Before you commit
Questions about mcp
No. Local MCP (stdio) is free: create an API key, paste the config from Settings → API Keys into Cursor. Your IDE installs the client from send.hatched.digital via npx. Hosted HTTP ($19/mo) is only for remote/cloud agents.
Ready when you are
Connect an IDE. Ship the first campaign.
Free local MCP with any API key — or Hosted HTTP MCP for $19/mo. First 200 emails on us.