Many AI agents support custom MCP connections, and the setup follows a similar pattern in all of them. You point the agent at the MCP server address and authorize it with your Elastic Email account. This guide walks you through it using Claude as an example. If you prefer a setup based on VS Code and GitHub Copilot, see our main article, Elastic Email MCP, which also lists every action the MCP server supports.
Before you start
You need an active Elastic Email account. The connector signs you in with your regular Elastic Email credentials, so you do not have to create an API key for this setup.
Not all of the available endpoints are supported on all Elastic Email pricing plans. For example, campaigns and contacts endpoints are not available for Email API plans.
The MCP server address, https://mcp.elasticemail.com, is used only to connect AI agents. It is not the address of the Elastic Email REST API and cannot be used as an API host in other integrations.
Adding Elastic Email as a custom connector in Claude
Go to Settings > Connectors and click Add custom connector.
Enter the Elastic Email MCP server address, https://mcp.elasticemail.com, give the connector a name, for example Elastic Email MCP, and click Continue.
In the next step, make sure the Sign in now and Register automatically options are selected. Both are usually detected for you. Confirm with Add.
A new browser window opens. Log in to your Elastic Email account and confirm that you want to finish connecting the connector. You are then redirected back to Claude.
Once Elastic Email appears on your list of connectors, you can start using it in your conversations. To make sure everything works, try a simple command first, for example asking whether the MCP connection is working. You should get a confirmation in reply.
Using the MCP server with other AI agents
The same server address works with any AI agent that supports MCP and can run in agent mode. The names of the settings differ between agents, but the steps are always the same: add a custom MCP server, point it at https://mcp.elasticemail.com, and authorize it either with your Elastic Email account or with an API key. Our main article, Elastic Email MCP, covers a full example based on VS Code and GitHub Copilot, including the API key method and the format of the configuration file.
Important notes
Only add connectors from sources you trust. A custom connector can act on your Elastic Email account on your behalf.
The more precise your prompt is, the less room for interpretation you leave to the agent. It is useful to review the requests before sending them, as you might notice inconsistencies in how the agent translated your request into API calls.
AI agents sometimes get stuck remembering earlier instructions and retrying them. Starting a new chat session usually resolves such issues.