Skip to main content
Glama
emailit-mcp

emailit-mcp

Official

Emailit MCP Server

An MCP server for the Emailit platform. Send emails, manage contacts, domains, templates, and more, directly from any MCP client like Claude Desktop, Cursor, or Claude Code.

This package runs locally with an Emailit API key. Emailit also hosts an MCP server at https://api.emailit.com/mcp that you sign in to with OAuth, no key or install needed: see emailit.com/docs/mcp.

Features

  • Emails — Send, list, get, cancel, update, and retry emails. Supports HTML, plain text, attachments, CC/BCC, reply-to, scheduling, tags, templates, and tracking.

  • Domains — Create, list, get, update, delete, and verify sender domains. Configure tracking and view DNS records.

  • API Keys — Create, list, get, update, and delete API keys.

  • Audiences — Create, list, get, update, and delete audiences for campaigns.

  • Contacts — Create, list, get, update, and delete contacts. Manage custom fields and audience subscriptions.

  • Templates — Create, list, get, update, delete, and publish reusable email templates.

  • Suppressions — Create, list, get, update, and delete email suppressions.

  • Webhooks — Create, list, get, update, and delete webhooks for event notifications.

Related MCP server: mailtarget

Setup

Create a free Emailit account and create an API key. To send to addresses outside of your own, you'll need to verify your domain.

Usage

The server supports two transport modes: stdio (default) and HTTP.

Stdio Transport (Default)

Claude Code

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

Cursor

Open the command palette and choose "Cursor Settings" > "MCP" > "Add new global MCP server".

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

Claude Desktop

Open Claude Desktop settings > "Developer" tab > "Edit Config".

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

HTTP Transport

Run the server over HTTP for remote or web-based integrations. In HTTP mode, each client authenticates by passing their Emailit API key as a Bearer token in the Authorization header.

Start the server:

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

The server will listen on http://127.0.0.1:3000 and expose the MCP endpoint at /mcp using Streamable HTTP.

Claude Code

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

Cursor

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

You can also set the port via the MCP_PORT environment variable:

MCP_PORT=3000 npx -y @emailit/emailit-mcp --http

Options

You can pass additional arguments to configure the server:

  • --key: Your Emailit API key (stdio mode only; HTTP mode uses the Bearer token from the client)

  • --sender: Default sender email address from a verified domain

  • --reply-to: Default reply-to email address (can be specified multiple times)

  • --http: Use HTTP transport instead of stdio (default: stdio)

  • --port: HTTP port when using --http (default: 3000, or MCP_PORT env var)

Environment variables:

  • EMAILIT_API_KEY: Your Emailit API key (required for stdio, optional for HTTP since clients pass it via Bearer token)

  • SENDER_EMAIL_ADDRESS: Default sender email address from a verified domain (optional)

  • REPLY_TO_EMAIL_ADDRESSES: Comma-separated reply-to email addresses (optional)

  • MCP_PORT: HTTP port when using --http (optional)

Note: If you don't provide a sender email address, the MCP server will ask you to provide one each time you send an email.

Local Development

  1. Clone this project and install dependencies:

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

EMAILIT_API_KEY=secret_xxx node src/index.js
  1. For HTTP mode:

node src/index.js --http --port 3000

License

MIT

Available Tools

47 tools
cancel-emailCancel EmailA

Cancel a scheduled or pending email. For scheduled emails, cancellation is only allowed if the scheduled time is at least 3 minutes in the future.

Inputs: id (required).

create-api-keyCreate API KeyB

Create a new API key in Emailit. The key value is only shown once upon creation, so you MUST display it to the user.

Inputs: name (required), scope, sending_domain_id.

create-audienceCreate AudienceC

Create a new audience for campaigns.

Inputs: name (required).

create-contactCreate ContactC

Create a new contact in your workspace.

Inputs: email (required), audiences, last_name, first_name, +2 more.

create-domainCreate DomainA

Create a new domain in Emailit. Returns DNS records that must be configured with your DNS provider for verification. You MUST display the DNS records to the user.

Inputs: name (required), track_loads, track_clicks.

create-suppressionCreate SuppressionB

Add an email address to the suppression list to prevent sending emails to that address.

Inputs: email (required), type, reason, keep_until.

create-templateCreate TemplateA

Create a new email template. Templates are automatically published if the alias doesn't exist yet; otherwise they remain as drafts.

Inputs: name (required), alias (required), from, html, +4 more.

create-webhookCreate WebhookB

Create a new webhook in your workspace. URL must be HTTPS and is validated against SSRF.

Inputs: url (required), name (required), events, enabled, +1 more.

delete-api-keyDelete API KeyA

Delete an API key from your Emailit account. Before using this tool, you MUST double-check with the user. Warn that this is irreversible and any services using it will lose access.

Inputs: id (required).

delete-audienceDelete AudienceA

Delete an audience and all its subscribers. Before using this tool, you MUST double-check with the user. Warn that this deletes all subscribers in the audience.

Inputs: id (required).

delete-contactDelete ContactA

Delete a contact and all associated subscriber records. Before using this tool, you MUST double-check with the user. Warn that this also deletes all subscriber records for this contact.

Inputs: id (required).

delete-domainDelete DomainA

Delete a domain from your Emailit account. Before using this tool, you MUST double-check with the user that they want to delete this domain. Warn that this is irreversible and will stop all email sending/receiving for that domain.

Inputs: id (required).

delete-suppressionDelete SuppressionA

Remove a suppression to allow sending emails to that address again. Before using this tool, confirm with the user.

Inputs: id (required).

delete-templateDelete TemplateA

Delete a template permanently. Before using this tool, you MUST double-check with the user. If it's the published version, no template will be published for that alias until another is published.

Inputs: id (required).

delete-webhookDelete WebhookA

Delete a webhook from your workspace. Before using this tool, you MUST double-check with the user. Can be identified by ID (wh_xxx) or name.

Inputs: id (required).

get-api-keyGet API KeyB

Retrieve information about a specific API key.

Inputs: id (required).

get-audienceGet AudienceB

Retrieve details of a specific audience.

Inputs: id (required).

get-contactGet ContactB

Retrieve information about a specific contact. Can be identified by ID (con_xxx) or email address.

Inputs: id (required).

get-domainGet DomainB

Retrieve information about a specific domain including DNS records and verification status.

Inputs: id (required).

get-emailGet EmailB

Retrieve a single email by ID, including headers, parsed body content, and attachments.

Inputs: id (required).

get-email-attachmentsGet Email AttachmentsB

Returns the attachment list for an email, with base64-encoded content.

Inputs: id (required).

get-email-bodyGet Email BodyA

Returns only the parsed body content (text and HTML) for an email.

Inputs: id (required).

get-email-metaGet Email MetaA

Returns email metadata with attachment info but without attachment content. Useful for inspecting without downloading large attachments.

Inputs: id (required).

get-email-rawGet Email RawB

Returns the full raw MIME message string along with email metadata.

Inputs: id (required).

get-suppressionGet SuppressionB

Retrieve a single suppression by ID or email address.

Inputs: id (required).

get-templateGet TemplateA

Retrieve a template by ID with full content and all other versions sharing the same alias.

Inputs: id (required).

get-webhookGet WebhookB

Retrieve information about a specific webhook.

Inputs: id (required).

list-api-keysList API KeysC

List all API keys in your Emailit account.

Inputs: page, limit.

list-audiencesList AudiencesC

List all audiences in your Emailit account.

Inputs: page, limit.

list-contactsList ContactsC

List all contacts in your workspace.

Inputs: page, limit.

list-domainsList DomainsB

List all domains in your Emailit account.

Inputs: page, limit.

list-emailsList EmailsA

List emails in your workspace with pagination and optional filtering by type (inbound/outbound).

Inputs: page, type, limit.

list-suppressionsList SuppressionsC

List all suppressions in your workspace.

Inputs: page, limit.

list-templatesList TemplatesA

List all published templates. Supports filtering by name, alias, and editor type.

Inputs: page, sort, order, per_page, +3 more.

list-webhooksList WebhooksC

List all webhooks in your workspace.

Inputs: page, limit.

publish-templatePublish TemplateA

Publish a template and automatically unpublish all other templates with the same alias. Only one template per alias can be published at a time.

Inputs: id (required).

retry-emailRetry EmailA

Retry an email that hard failed, errored, or was held. Creates a duplicate of the original email and sends it again with a new ID.

Inputs: id (required).

send-emailSend EmailC

Send an email via Emailit. Supports HTML, plain text, templates, variables, attachments, CC/BCC, scheduling, and tracking.

Inputs: to (required), cc, bcc, from, +11 more.

update-api-keyUpdate API KeyB

Update the name of an existing API key.

Inputs: id (required), name (required).

update-audienceUpdate AudienceC

Update an audience's name.

Inputs: id (required), name (required).

update-contactUpdate ContactC

Update an existing contact. Can be identified by ID (con_xxx) or email address.

Inputs: id (required), email, last_name, first_name, +2 more.

update-domainUpdate DomainC

Update an existing domain's tracking and configuration settings.

Inputs: id (required), inbound_key, track_loads, track_clicks, +1 more.

update-emailUpdate Scheduled EmailA

Update a scheduled email's send time. Only works for emails with status "scheduled" and only if the current scheduled time is at least 3 minutes in the future.

Inputs: id (required), scheduled_at (required).

update-suppressionUpdate SuppressionB

Update an existing suppression. At least one field must be provided.

Inputs: id (required), type, email, reason, +1 more.

update-templateUpdate TemplateA

Update an existing template. All fields are optional. Does not change published status.

Inputs: id (required), from, html, name, +5 more.

update-webhookUpdate WebhookB

Update an existing webhook. Can be identified by ID (wh_xxx) or name. At least one field must be provided.

Inputs: id (required), url, name, events, +2 more.

verify-domainVerify DomainA

Trigger domain DNS verification. Checks all DNS records (MX, SPF, DKIM, DMARC) and updates the domain's verification status.

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and descriptions distinguish the email retrieval variants. However, get-email, get-email-raw, get-email-body, get-email-attachments, and get-email-meta intentionally overlap by returning different views of the same resource, which could cause occasional misselection.

    Naming Consistency5/5

    Tool names consistently use lowercase kebab-case with a predictable verb-resource pattern such as create-domain, get-domain, list-domains, update-domain, and delete-domain. Pluralization for list operations is also consistent across resources.

    Tool Count2/5

    At 47 tools, the surface is very heavy for an MCP server and exceeds the practical range for easy tool selection. While the breadth reflects a full email platform, the count is excessive and likely to increase cognitive load and selection errors.

    Completeness5/5

    The tool set covers full lifecycle management for domains, API keys, audiences, contacts, suppressions, templates, and webhooks, plus sending and handling emails. No obvious domain-critical operation appears missing.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.
      16
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Mailtarget that exposes tools to discover and call management API endpoints and send transactional emails via the Transmission API.
      2 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Remote MCP server for the Transmit email platform, enabling email sending, contact management, template and campaign operations via natural language.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables sending transactional email and campaigns, managing contacts and templates, and reading delivery reports and wallet usage from any MCP client.
      MIT