MCP documentation
Email Love is a native MCP server. Point any AI tool at one URL and it can search the library, pull cleaned HTML, and walk lifecycle journeys. Prefer a plain REST API? See the API docs.
Overview
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to outside tools and data. The Email Love MCP brings the entire library, 400,000+ marketing emails, lifecycle journeys, and brand-level analytics, directly into Claude, ChatGPT, Cursor, Claude Code, and any MCP-enabled assistant. In plain terms: it turns your AI into an email marketing expert that has actually seen thousands of real campaigns, and can pull up the exact ones you need, in the middle of whatever you are working on. No tab-switching, no copy-paste.
Free with an Email Love account. Register free →
Connect
Setup is a one-time, two-minute job and the URL is always the same: https://chat.emaillove.com/mcp. You add it as a connector, sign in with your Email Love account, and click Allow. Secure by design: you log in through Email Love, so you never paste a secret key.
In Claude
- Open Settings › Connectors.
- Click Add custom connector.
- Paste the URL. Leave Client ID and Secret blank.
- Click Add, then sign in and click Allow.
- On Claude Desktop only: quit and reopen so it picks up the new tools.
In Claude Code
claude mcp add --transport http email-love https://chat.emaillove.com/mcp
Works with any MCP-enabled assistant (ChatGPT, Cursor, and more). In Claude.ai and Claude Desktop, results render as inline cards and carousels with real email screenshots; CLI tools like Claude Code return the structured data.
Tools
You don't memorize commands, you just ask. Under the hood, these tools do the work:
| Tool | Arguments | What it does |
|---|---|---|
| search_emails | query?, brand?, category?, limit? (1-25, default 10) | Search the email library. Returns matching email summaries. |
| fetch_email | id (integer) | Full details for one email: brand, categories, lifecycle stages, screenshot. |
| search_brands | query?, limit? (1-25, default 10) | Find brands. Omit query for the top brands by email count. |
| list_journeys | limit? (1-50, default 30) | List brands that have a curated lifecycle journey. |
| get_journey | brand (slug), emails_per_stage? (1-10, default 5) | One brand's lifecycle flow, by stage. The most differentiated tool. |
| get_brand_insights | brand (slug) | Brand-level analytics: ESP, send timing, subject-line patterns, content metrics, deliverability. |
| search ยท fetch | query / id | Convenience aliases for search_emails / fetch_email. |
Signed-in users also get list_collections, get_collection, and list_liked_emails for their own saved Collections and likes.
Example prompts
A few that show what it can do:
- “Compare REI and Patagonia’s email programs: how often they send, what ESP they use, and how their subject lines differ.”
- “Show me 3 post-purchase emails from DTC apparel brands. Which one has the cleanest design?”
- “Walk me through MeUndies’ winback flow.”
- “What words and emojis does Fabletics use most in its subject lines, and how long are they on average?”
- “When do Lululemon, Alo Yoga and Vuori send their emails? Compare their days and times.”
Privacy
When you connect, Email Love receives only what it needs: your Email Love user id and email (so we know whose account is asking) and your connecting IP for a couple of minutes (for rate-limiting, then discarded). We do not receive your conversation, your prompts, or anything beyond the specific tool call your assistant makes. Your access token lasts 30 days; revoke the connector in your AI tool any time, or change your Email Love password to invalidate all sessions.
Two MCPs
Email Love has two MCPs that do two different jobs. This is the research MCP: it connects to the library, brand insights and journeys, to help you find inspiration and decide what to send. The separate generation MCP (Growth plan and up) builds on-brand emails from the design system you sync with the Email Love Figma Plugin, to help you design and ship. Research a winback flow with one, then generate your own from your components with the other.
Questions? hello@emaillove.com