---
title: "Elastic Email MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/elastic-email/
description: "Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4."
---

# Elastic Email MCP: review, setup & limitations · Undominated.ai

> Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.

[← Explore all mcp servers](/mcp-servers/)

EMAIL / Elastic Email

# Elastic Email MCP

Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/ElasticEmail/elasticemail-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 4 linked sources
 Publisher Elastic Email
 Licence [MIT ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/LICENSE)
 Revision 1782b6dde78f
 [Read what was—and wasn’t—checked ↓](#review)

“Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.”

 [Elastic Email · upstream description ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.
- The setup documentation makes this operating boundary explicit: The API key needs the requested business-operation permissions and access to list API keys; the middleware validates it against /v4/security/apikeys.

### A good fit for

 - Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.
- Build the reviewed .NET project as the README describes and run dotnet run --project src/ElasticEmail.Mcp.Service.csproj; connect an HTTP MCP client to http://localhost:5001/ with X-Auth-Token on every request.

### Weigh up before choosing

 - The source binds plain HTTP on 0.0.0.0:5001 and caches supplied keys in process memory. Keep access local/private or terminate TLS with an appropriately restricted proxy; do not interpret per-request authentication as no credential handling.
- Package/container parity with the pinned source and transitive dependency security were not established.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md
- LICENSE
- src/Authorization/AuthorizationMiddleware.cs
- src/Program.cs

### Our findings

 - The API key needs the requested business-operation permissions and access to list API keys; the middleware validates it against /v4/security/apikeys.
- The source binds plain HTTP on 0.0.0.0:5001 and caches supplied keys in process memory. Keep access local/private or terminate TLS with an appropriately restricted proxy; do not interpret per-request authentication as no credential handling.

### Not established by this review

 - No server installation, authentication, live tool execution or isolation test was performed.
- Package/container parity with the pinned source and transitive dependency security were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/README.md)
 - Build the reviewed .NET project as the README describes and run dotnet run --project src/ElasticEmail.Mcp.Service.csproj; connect an HTTP MCP client to http://localhost:5001/ with X-Auth-Token on every request.
- Verify the connected account, available tools and target resource before authorizing mutations.

### Before you start

 - .NET SDK 10.0 or later to build and run the reviewed source.
- A Streamable HTTP MCP client able to supply X-Auth-Token.
- The API key needs the requested business-operation permissions and access to list API keys; the middleware validates it against /v4/security/apikeys.

### Compatibility

An MCP client supporting Streamable HTTP and an X-Auth-Token request header.

### Implementation

C#

### Transports

Streamable HTTP

### Self-hosted HTTP service with Elastic Email API credentials

 - The API key needs the requested business-operation permissions and access to list API keys; the middleware validates it against /v4/security/apikeys.

### Cost model

Publisher service entitlements, API usage and infrastructure charges apply where applicable; the MCP source licence does not include external services.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned publisher README and migration notices ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/README.md) Checked 2026-10-14 https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/README.md Supports: description, setup, capabilities, review, limitations
- [Licence text at the reviewed commit ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/LICENSE) Checked 2026-10-14 https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/LICENSE Supports: license
- [Pinned implementation inspected for launch or permission boundary ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/src/Authorization/AuthorizationMiddleware.cs) Checked 2026-10-14 https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/src/Authorization/AuthorizationMiddleware.cs Supports: review, install, access, limitations
- [Pinned implementation inspected for launch or permission boundary ↗](https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/src/Program.cs) Checked 2026-10-14 https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/src/Program.cs Supports: review, install, access, limitations

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Mailgun MCP ↗ Send email, diagnose deliverability and manage domains, templates, webhooks and other Mailgun account operations.](/mcp-servers/mailgun/)[### Mailtrap MCP ↗ Send or sandbox email, inspect delivery logs and statistics, and manage templates, domains, contacts and account resources.](/mcp-servers/mailtrap/)[### Klaviyo MCP Server ↗ Klaviyo's official remote MCP server at mcp.klaviyo.com wraps Klaviyo's APIs for campaign reporting, flow comparison, profile inspection and campaign creation, connecting over Streamable HTTP with OAuth and dynamic client registration. Custom connections can disable write tools, restrict tools by API scope, exclude tools that read user-generated content and opt into beta tools through query parameters before connecting.](/mcp-servers/klaviyo/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
