EMAIL / Elastic Email
Elastic Email MCP
Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.
“Send transactional or bulk email and manage contacts, campaigns, lists and statistics through Elastic Email API v4.”
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.
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.
- 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.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/README.md
Supports: description, setup, capabilities, review, limitations
https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/LICENSE
Supports: license
https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/src/Authorization/AuthorizationMiddleware.cs
Supports: review, install, access, limitations
https://github.com/ElasticEmail/elasticemail-mcp-server/blob/1782b6dde78fa637cd34a20caeb4c9a5106f0918/src/Program.cs
Supports: review, install, access, limitations