Elastic Email Unlocks AI-powered Assistant with the Email MCP Server

Updated: October 2026

The Elastic Email MCP Server lets you run your email marketing and sending from the AI assistant you already use. Ask Claude, ChatGPT, GitHub Copilot or Cursor to create a campaign, check its results, verify a domain or clean up a contact list, and the assistant does it in your Elastic Email account. No dashboard clicks, no API calls to write. You describe the task in plain language, and the agent turns it into the right action.

TL;DR - Elastic Email MCP Server at a glance

• What it is: a server that connects MCP-compatible AI assistants (Claude, ChatGPT, GitHub Copilot, Cursor and others) to your Elastic Email account.
• What it does: campaigns and campaign statistics, transactional and bulk sending, contacts, lists and segments, templates, sending domains, suppressions and sent-email lookups.
• Server address: https://mcp.elasticemail.com
• How you sign in: with your Elastic Email account (no API key needed) or with an API key.
• Setup time: a few minutes. In Claude, add it as a custom connector; in other tools, add it as an MCP server in agent mode.
• Plan note: campaign and contact tools aren't available on Email API plans.

What is the Elastic Email MCP Server?

The Elastic Email MCP Server is the bridge between AI agents and your Elastic Email account. It's built on the Model Context Protocol (MCP), an open standard for connecting AI applications to external tools and data.

When you ask your assistant to do something, such as "pause my Friday campaign", the agent picks the matching Elastic Email tool, fills in the details and runs it. You get the result back in the chat.

The agent can only do what your access allows. If you connect with your account, it acts with your account's permissions. If you connect with an API key, it's limited to the permissions you gave that key.

What can you do with the Elastic Email MCP Server?

The server gives your AI assistant tools across seven areas, from email campaigns to transactional sending. The full tool reference is in the MCP developer documentation.

There's also a health check tool, so you can ask the agent whether the connection is working at any time.

When the agent creates a campaign, it sends straight away by default. If you want to review it first, ask for a draft or a paused campaign. A campaign needs a name, subject, content (plain text or HTML) and a From address. Attachments and a send schedule are optional.

Example prompts that save you time

• "Show me the contact lists in my account."
• "Send a welcome email to email_address from email_address using content."
• "Create a draft campaign called campaign_name for list_name from email_address."
• "How did my last campaign perform? Show opens, clicks and bounces."
• "Add domain as a sending domain, then verify it."
• "Add these addresses to my suppression list as unsubscribed: email_addresses."
• "Find the email with transaction ID transaction_id and show me its status."

Before you start

• An active Elastic Email account. Sign up for free if you don't have one yet.
• An MCP-compatible AI tool that supports agent mode or custom connectors, such as Claude, ChatGPT, VS Code with GitHub Copilot, Cursor or Gemini CLI. Check your AI tool's plan, as some only offer custom MCP connections on paid tiers.
• The right Elastic Email plan for what you want to do. Not every tool is available on every plan. Campaign and contact tools aren't available on Email API plans.
• The server address: https://mcp.elasticemail.com

How to connect the Elastic Email MCP Server

Choose how you want to sign in:

If you use an API key, give it view and modify access to Account, Templates, Campaigns, Contacts, Files and Send HTTP, plus at least view access to Access Tokens. Never share the key with anyone you don't trust.

Connect to Claude

1. In Claude, go to Settings > Connectors and click Add custom connector.
2. Enter the server address https://mcp.elasticemail.com, give the connector a name (for example, "Elastic Email MCP") and click Continue.
3. Make sure Sign in now and Register automatically are selected, then click Add.
4. Log in to Elastic Email in the browser window that opens and confirm the connection. You'll be taken back to Claude.
5. Test it: ask Claude, "Is the Elastic Email MCP connection working?"

Full walkthrough with screenshots: How to connect the Elastic Email MCP Server to Claude.

Connect to VS Code with GitHub Copilot

1. Install VS Code and the GitHub Copilot and GitHub Copilot Chat extensions, then sign in to GitHub.
2. Open the chat panel and switch it to agent mode.
3. Open the command palette, search for "MCP" and open your MCP user configuration.
4. Paste the configuration below and save the file. The Start option only appears after you save.
5. Start the server, then ask the agent, "Is MCP working?"

{
  "servers": {
    "elasticemail.mcp": {
      "url": "https://mcp.elasticemail.com",
      "headers": {
        "X-Auth-Token": "YOUR_API_KEY"
      }
    }
  }
}

{
  "servers": {
    "elasticemail.mcp": {
      "url": "https://mcp.elasticemail.com",
      "headers": {
        "X-Auth-Token": "YOUR_API_KEY"
      }
    }
  }
}

To sign in with your account instead, remove the headers section. When you start the server, VS Code opens the Elastic Email login page and returns you to the editor once you've signed in.

Connect other AI agents

The same address works with any MCP-compatible agent that supports agent mode, including ChatGPT, Cursor and Gemini CLI. Add a custom MCP server pointing to https://mcp.elasticemail.com, then authorize it with your account or an API key. See Elastic Email MCP in our Help Center for details.

Tips for reliable results