ElasticEmail MCP connector
Connect ElasticEmail to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can list, create, pause and update email campaigns, import and clean up contacts, and verify sending domains, with every action logged under the person who asked.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
110 tools
How to connect
How to connect ElasticEmail to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ElasticEmail once
-
Open Connections, choose Add connection, and pick ElasticEmail.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an ElasticEmail API key. One person generates a token in ElasticEmail and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
ElasticEmail MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
ElasticEmail MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
ElasticEmail MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect ElasticEmail to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with ElasticEmail through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Set up the next campaign from a brief
Describe the send in plain words and have the campaign created in ElasticEmail, then check the details before anything goes out. Pause it from the same place if a date slips.
-
Sales
Load event signups into ElasticEmail
Paste the signups from a webinar or trade show and import them as ElasticEmail contacts in one go, ready for the follow-up sequence.
-
Support
Fix a contact record after a complaint
When someone writes in asking to change their details or stop receiving mail, look up their ElasticEmail contact and update or remove it while they are still on the line.
-
Lifecycle
Start an automation for a new segment
Trigger an ElasticEmail automation for the contacts who just qualified, without opening the dashboard or waiting for someone with admin access.
-
IT
Check sending domains before a launch
List every domain connected to ElasticEmail, see which ones are still unverified or restricted, and set the right one as the default before marketing hits send.
-
Operations
Export and prune the contact list
Pull an export of ElasticEmail contacts, check how far it has got, and remove stale or duplicate records in bulk once the review is done.
Try asking
- “Pause the spring promo campaign and tell me what is scheduled next”
- “Import these 40 webinar signups as contacts tagged webinar-may”
- “Which of our sending domains are still unverified?”
Compare
Elaichi vs Zapier MCP vs Composio for ElasticEmail
All three can connect ElasticEmail to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ElasticEmail tools | Allow or restrict single ElasticEmail tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ElasticEmail call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
ElasticEmail tools for your AI agents
110 tools are ready to call through Elaichi's MCP endpoint the moment you connect ElasticEmail, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting ElasticEmail gets you
6 screens from the product, each doing one job for your ElasticEmail account.
The agent
Ask about campaigns and contacts in plain words.
Three prompts to start, answers pulled from live ElasticEmail campaigns and contact lists.
- campaigns
- contacts
- domains
- exports
Ask Elaichi to work across your apps.
Pause the spring promo campaign and tell me what is scheduled next
Import these 40 webinar signups as contacts tagged webinar-may
Which of our sending domains are still unverified?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches ElasticEmail from any client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
110 ElasticEmail tools, ready without writing code.
Campaigns, contacts and domains covered end to end, with nothing for an engineer to build.
- List all ElasticEmail campaigns
- Create a ElasticEmail campaign
- Get single ElasticEmail campaign by ID
- Update a ElasticEmail campaign by ID
ElaichiToolsToolboxes
Each team gets its own ElasticEmail toolbox.
Marketing runs campaigns, sales imports contacts, IT handles domains, each from a scoped toolbox.
- Marketing
- Sales
- Support
- Lifecycle
ElaichiToolboxesShared connections
Share one ElasticEmail account, never the key.
One person connects, shares with teams, and nobody else ever handles the API key.
- Marketing
- Sales EMEA
- Lifecycle
- Support
ElaichiConnectionsAudit log
Every ElasticEmail action is logged with a name.
When, who, what happened and which campaign or contact, kept in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Schedules run the work, people approve it.
ElasticEmail campaign results are fetched, grouped, drafted into a digest, approved, then posted back.
ElasticEmail digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch campaigns
ElasticEmail
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
ElasticEmail
Queued
Collections and dashboards
ElasticEmail health numbers arrive before anyone asks.
Four metrics, 14 days of new contacts, a team breakdown, refreshed on schedule, no model involved.
ElasticEmail health
Refreshed 4 minutes ago · every 15 minutes · from the campaigns collection
Campaigns
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Campaigns created
Last 14 days
By team
Share of activity
Marketing 34%
Sales EMEA 27%
Lifecycle 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect ElasticEmail to Claude?
Two steps. In Elaichi, choose ElasticEmail and paste in your ElasticEmail API key, which is the only sign-in step, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself and ElasticEmail is available from then on.
Does ElasticEmail work with ChatGPT and Cursor as well as Claude?
Yes. Once ElasticEmail is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect ElasticEmail once and every client you use picks it up.
What can an AI agent actually do with my ElasticEmail data?
It can list your ElasticEmail campaigns, create or update one, pause it, or trigger an automation. It can look up, add, change and remove contacts, import a batch or export the list, and it can check which sending domains are verified and set the default. Short, concrete asks such as "pause the May newsletter" work better than long paragraphs.
Does connecting ElasticEmail give the AI access to every campaign and contact?
The AI gets exactly what the person who signed in to ElasticEmail can already see, because every call runs under that person's own key and account. Elaichi can narrow that further, for example to reading campaigns but not deleting contacts, and it can never widen it beyond what ElasticEmail itself allows.
Can I stop an agent from deleting or changing things in ElasticEmail?
Yes. Restrictions in Elaichi apply per action, so you can allow reading ElasticEmail campaigns and contacts while blocking deletes, bulk removals or domain changes. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a ElasticEmail connection when someone leaves?
Offboarding that person in Elaichi ends their access to ElasticEmail through every client at once. A shared ElasticEmail connection keeps working for everyone else on the team. If you want ElasticEmail gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the ElasticEmail MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ElasticEmail is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for ElasticEmail?
Yes. Both let Claude, ChatGPT or Cursor use ElasticEmail. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ElasticEmail call.
How is Elaichi different from Composio for ElasticEmail?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ElasticEmail: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put ElasticEmail in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.