MCP server

Drive EmailBuilder from Claude Desktop or any MCP-compatible client. List, create, render, and update templates and pages from inside your AI assistant.

EmailBuilder ships an MCP (Model Context Protocol) server that exposes the editor's primitives — emails, pages, modules, content sources — as tools your AI assistant can call directly. Connect it to Claude Desktop (or any MCP client) and you can manage templates from a chat.

This is the closest thing EmailBuilder has to a public API today, and it's the recommended way to integrate.

What you can do

The MCP server exposes tools for:

Domain	Tools
Projects	`list_projects`, `set_project`
Emails	`list_emails`, `get_email`, `create_email`, `update_email`, `delete_email`, `render_email_html`, `validate_mjml`
Pages	`list_pages`, `get_page`, `create_page`, `update_page`, `delete_page`
Modules	`list_modules`, `get_module`, `create_module`, `update_module`, `delete_module`
Content sources	`list_content_sources`, `get_content_source`, list source items
Branding	`get_branding`

Each tool maps directly to the API the editor uses. Whatever you can do in the EmailBuilder UI for a single project, you can do via MCP.

Connect it to Claude Desktop

Sign in to app.emailbuilder.ai.
Go to Account → Integrations → API Keys.
Click Generate new key, name it ("Claude MCP"), and copy the key.
Open Claude Desktop → Settings → Developer → Edit config. Add EmailBuilder as a remote MCP server:

{
  "mcpServers": {
    "emailbuilder": {
      "transport": {
        "type": "sse",
        "url": "https://mcp.emailbuilder.ai/sse",
        "headers": {
          "Authorization": "Bearer eb_YOUR_API_KEY_HERE"
        }
      }
    }
  }
}

Restart Claude Desktop. The new tools appear in the tool tray.

A typical session

A new session always starts the same way: list your projects, pick one. From then on, all tool calls are scoped to that project.

You: List my projects.
Claude → list_projects → returns 3 projects

You: Switch to "Acme Newsletter".
Claude → set_project(id)

You: Create a welcome email with our blue brand colour and the standard footer.
Claude → get_branding (gets colour palette)
       → list_modules (finds footer)
       → create_email(mjml=...)

You: Render it to HTML so I can preview.
Claude → render_email_html(email_id) → returns rendered HTML

The MCP server reads get_branding to find your brand colours and applies them automatically — you don't have to paste your hex codes into every prompt.

Project scoping

Every API key acts within an account, but the MCP session needs to know which project within that account to work in. Multi-project accounts (one per brand or client) get clean isolation: a session set to Project A can't see or modify Project B's emails.

You can switch projects mid-session with set_project. All subsequent tools re-scope.

Auth model

Each API key is tied to one EmailBuilder account.
Calls are server-to-server: the key never leaves Claude Desktop and your machine.
Keys are stored hashed on our side (SHA-256). You can't retrieve a key you've lost — generate a new one.
The Account → Integrations → API Keys page shows last-used timestamp per key. Rotate anything that's been idle for months.

Health and limits

The MCP server runs at https://mcp.emailbuilder.ai with SSE transport.
One session per concurrent connection. Disconnect releases the session immediately.
Rate limits track your account's normal API quotas — see your plan page for current numbers.

When to use MCP vs other paths

Want to …	Use
Build and send emails by hand	The web app at app.emailbuilder.ai
Insert a saved template into Gmail	The Gmail add-on
Drive EmailBuilder from an AI workflow (Claude, Cursor, custom MCP clients)	This MCP server
Trigger a send from an external system	Not available as a public REST endpoint yet — use MCP from a script-style AI session, or contact us about your use case

A public REST API for sending is on our roadmap. Until then, MCP plus the Gmail/Outlook add-ons cover most automation needs.