What is the Emailit MCP Server?

The Emailit MCP Server is an open-source Model Context Protocol server that connects AI assistants directly to Emailit.

It lets you send emails, manage contacts, domains, templates, and more through natural language — right from Claude, Cursor, or any MCP-compatible client.

• Package: @emailit/emailit-mcp
• Runtime: Node.js 18+
• License: MIT
• Repository: github.com/emailit/emailit-mcp

Prerequisites

• An Emailit account
• An API key
• A verified sending domain
• Node.js 18 or later

Transport modes

The server supports two transport modes:

Stdio (default)

The MCP client starts the server as a subprocess and communicates over standard input/output. The API key is passed via an environment variable or CLI argument. This is the simplest option and works with all major clients.

HTTP (Streamable HTTP)

For remote or web-based integrations, the server runs as an HTTP server using Streamable HTTP transport. Clients authenticate per-session by passing their API key as a Bearer token in the Authorization header. The endpoint is exposed at /mcp.

Installation & configuration

Claude Code (Stdio)

claude mcp add emailit \
  -e EMAILIT_API_KEY=your_api_key \
  -- npx -y @emailit/emailit-mcp

Claude Code (HTTP)

Start the server first:

npx -y @emailit/emailit-mcp --http --port 3000

Then register it:

claude mcp add emailit \
  --transport http http://127.0.0.1:3000/mcp \
  --header "Authorization: Bearer your_api_key"

Cursor (Stdio)

Open the command palette and choose Cursor Settings → MCP → Add new global MCP server, then paste:

{
  "mcpServers": {
    "emailit": {
      "command": "npx",
      "args": ["-y", "@emailit/emailit-mcp"],
      "env": {
        "EMAILIT_API_KEY": "your_api_key"
      }
    }
  }
}

Cursor (HTTP)

Start the server, then add:

{
  "mcpServers": {
    "emailit": {
      "url": "http://127.0.0.1:3000/mcp",
      "headers": {
        "Authorization": "Bearer your_api_key"
      }
    }
  }
}

Claude Desktop (Stdio)

Open Claude Desktop settings → Developer tab → Edit Config, then paste:

{
  "mcpServers": {
    "emailit": {
      "command": "npx",
      "args": ["-y", "@emailit/emailit-mcp"],
      "env": {
        "EMAILIT_API_KEY": "your_api_key"
      }
    }
  }
}

CLI options

Environment variables

Tip: If you don’t provide a sender email address, the MCP server will ask for one each time you send an email.

Available tools

The server exposes 47 tools across 8 categories.

Emails (10 tools)

Domains (6 tools)

API Keys (5 tools)

Audiences (5 tools)

Contacts (5 tools)

Templates (6 tools)

Suppressions (5 tools)

Webhooks (5 tools)

Usage examples

Send a simple email

Ask your AI assistant:

“Send a welcome email to john@example.com with the subject ‘Welcome!’”

The AI calls send-email with:

{
  "from": "hello@mydomain.com",
  "to": "john@example.com",
  "subject": "Welcome!",
  "html": "<h1>Welcome!</h1><p>Thanks for signing up.</p>"
}

Send with a template and variables

“Send the welcome-email template to sarah@example.com with her name as Sarah.”

{
  "from": "hello@mydomain.com",
  "to": "sarah@example.com",
  "template": "welcome-email",
  "variables": { "name": "Sarah" }
}

Schedule an email

“Schedule a reminder email to team@company.com for tomorrow at 9am.”

{
  "from": "reminders@mydomain.com",
  "to": "team@company.com",
  "subject": "Daily Standup Reminder",
  "text": "Don't forget the standup at 9:30!",
  "scheduled_at": "tomorrow at 9am"
}

Send with attachments

“Send an email to accounting@company.com with the invoice PDF attached.”

{
  "from": "billing@mydomain.com",
  "to": "accounting@company.com",
  "subject": "Monthly Invoice",
  "html": "<p>Please find the invoice attached.</p>",
  "attachments": [
    {
      "filename": "invoice-2026-05.pdf",
      "url": "https://example.com/invoices/2026-05.pdf"
    }
  ]
}

Manage domains

“Add my domain mail.example.com and show me the DNS records.”

The AI calls create-domain and displays the required DNS records for you to configure with your DNS provider.

“Verify my domain.”

The AI calls verify-domain to check DNS propagation and reports back the verification status.

Manage contacts

“Add Jane Smith (jane@example.com) to audience aud_abc123.”

{
  "email": "jane@example.com",
  "first_name": "Jane",
  "last_name": "Smith",
  "audiences": ["aud_abc123"]
}

Manage templates

“Create a newsletter template with alias monthly-newsletter.”

{
  "name": "Monthly Newsletter",
  "alias": "monthly-newsletter",
  "subject": "Monthly Update {{month}}",
  "html": "<h1>{{month}} Update</h1>..."
}

Manage suppressions

“Suppress bounced@example.com for too many hard bounces.”

{
  "email": "bounced@example.com",
  "type": "bounce",
  "reason": "too many hard bounces"
}

Set up webhooks

“Create a webhook that sends delivery and bounce events to my endpoint.”

{
  "name": "Delivery Tracker",
  "url": "https://myapp.com/webhooks/email",
  "events": ["email.delivered", "email.bounced"]
}

Security notes

• API keys should never be committed to version control.
• In stdio mode, the API key is stored in the MCP client’s configuration.
• In HTTP mode, clients pass the API key per-session via Bearer token.
• Webhook URLs are validated against SSRF before creation.
• Delete operations prompt the AI to confirm with you first.

Troubleshooting

“API key required for stdio mode” Set the EMAILIT_API_KEY environment variable or pass --key.

Domain not verified Configure DNS records from create-domain output, then call verify-domain.

Email rejected / not sending Ensure domain is verified and sender address uses that domain.

Scheduled email can’t be canceled Must be at least 3 minutes before the scheduled time.

Retry fails Only hard-failed, errored, held, or suppressed emails can be retried.

Local development

git clone https://github.com/emailit/emailit-mcp.git
cd emailit-mcp
npm install

# Run in stdio mode
EMAILIT_API_KEY=your_key node src/index.js

# Run in HTTP mode
node src/index.js --http --port 3000

For more details, see the GitHub repository.