elasticemail

This MCP server provides a bridge to the Elastic Email API. It exposes a set of tools under categories such as HealthCheck, CampaignManagement, SegmentsManagement, TemplateManagement, EmailSending, and ContactsManagement. These tools allow you to verify API availability, manage campaigns and templates, create and manage contact lists and segments, and send both bulk and transactional emails. To use them, ensure your agent configuration points to http://localhost:5001/ with the correct X-Auth-Token header containing your API key. In VS Code, open the agent settings, select the Elastic Email MCP server from the list of tools, and start the agent to begin issuing tool calls against the Elastic Email API.

Example agent configuration snippet: {"my-server-unique-number": { "url": "http://localhost:5001/", "headers": { "X-Auth-Token": <api_key> } }}

Prerequisites:

• .NET 10 SDK or higher installed on your machine
• Access to the Elastic Email API and a valid API key
• Open port 5001 for HTTP traffic

Installation steps:

1. Clone or download the MCP server repository.
2. Ensure you have a suitable directory structure and the MCP Server project file ElasticEmail.MCP.Server.csproj is present at ElasticEmail.MCP.Server/ElasticEmail.MCP.Server.csproj.
3. Set up your environment variables. Create a file or export ELASTICEMAIL_API_KEY with your Elastic Email API key and ensure port 5001 is open.
4. Build or run the server using the command: dotnet run --project ElasticEmail.MCP.Server/ElasticEmail.MCP.Server.csproj
5. Verify the server is listening on port 5001 (HTTP) and that you can reach http://localhost:5001/.

Notes:

• You might want to configure a reverse proxy or TLS termination in production.
• Ensure your Elastic Email account has the necessary permissions for the requested operations (campaigns, templates, contacts, etc.).

Common issues and tips:

• If the server fails to start, verify that the .NET 10 SDK is installed and that the Elastic Email API key is correctly provided via ELASTICEMAIL_API_KEY.
• Ensure port 5001 is not blocked by firewall or security groups.
• The agent example uses an X-Auth-Token header; adapt its value to your actual API key.
• Some operations may require additional permissions on the Elastic Email account (e.g., creating campaigns or uploading contacts).
• If you update templates or campaigns, you may need to refresh credentials or re-authenticate in the agent interface.