Marketing Automation
Omnisend MCP connector
The Omnisend connector lets Claude, ChatGPT, Cursor, or any MCP client read and update your Omnisend contacts, tags, products, categories, and campaigns, with each person signed in as themselves and every change recorded in an audit log.
-
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.
How to connect
How to connect Omnisend to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Omnisend once
-
Open Connections, choose Add connection, and pick Omnisend.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Omnisend API key. One person generates a token in Omnisend 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.
Connect Omnisend to 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.
Connect Omnisend to 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.
Connect Omnisend to 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 Omnisend 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 Omnisend through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Draft the next campaign from a request
Describe the promotion in plain words and have the agent set up the campaign in Omnisend, ready for you to review before anything is sent.
-
Marketing
Tag a segment before a send
Ask for every contact who matches a description to be tagged in one go, so the audience is ready in Omnisend when the campaign is.
-
Support
Catch a contact up after a conversation
After a chat or a phone call, have the agent update the contact record in Omnisend and add or remove the tags that reflect what happened.
-
Ecommerce
Keep the product catalog current
Add new products, fix prices and descriptions, and tidy product categories in Omnisend without leaving the conversation.
-
Operations
Load a spreadsheet of subscribers in one batch
Hand over a list of new contacts and have them created in Omnisend as a single batch, then check on the batch to confirm it finished.
-
Leadership
See what went out this month
Ask which campaigns were sent from Omnisend recently and how the contact list has grown, and get a plain answer pulled from live records.
Try asking
- “How many Omnisend contacts were created in the last 14 days?”
- “Add the VIP tag to these Omnisend contacts.”
- “List Omnisend products updated this week.”
AI tools
Omnisend tools for your AI agents
82 tools are ready to call through Elaichi's MCP endpoint the moment you connect Omnisend, 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 Omnisend gets you
6 screens from the product, each doing one job for your Omnisend account.
The agent
Ask about Omnisend contacts in plain language.
Starter prompts read live Omnisend contacts, products and tags and answer in seconds.
- contacts
- tags
- products
- brands
Ask Elaichi to work across your apps.
How many Omnisend contacts were created in the last 14 days?
Add the VIP tag to these Omnisend contacts.
List Omnisend products updated this week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Omnisend here.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
82 Omnisend tools are ready to call.
Contacts, tags, products and brands are covered, with no custom code to write.
- List all Omnisend contacts
- Create a Omnisend contact
- Get single Omnisend contact by ID
- Update a Omnisend contact by ID
Toolboxes
Every team gets its own Omnisend toolbox.
Curate one toolbox per team so each group sees only relevant Omnisend tools.
- Lifecycle Marketing
- Ecommerce
- Customer Support
- Growth
Shared connections
Teammates use Omnisend without seeing a key.
Each connection shows who added the account and which teams and members share it.
- Lifecycle EMEA
- Retail US
- Support
- Growth
Audit log
Every Omnisend call is written down.
When, who, what happened, type and resource for each contact and product change.
- When
- Who
- What happened
- Type
Launching 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
A schedule drafts your Omnisend digest.
Fetch contacts, group them, draft a digest, get approval, post back to Omnisend.
Omnisend digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contacts
Omnisend
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
Omnisend
Queued
Collections and dashboards
Omnisend contact growth, counted not guessed.
Four metrics, 14 days of contacts created and a team breakdown, refreshed on schedule.
Omnisend health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Tags
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Lifecycle EMEA 34%
Retail US 27%
Support 21%
Growth 18%
FAQ
Frequently asked questions
How do I connect Omnisend to Claude?
First connect Omnisend in Elaichi by pasting the API key from your Omnisend account settings. 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. Sign in to Elaichi when prompted and Omnisend is available in your conversation.
Does Omnisend work with ChatGPT and Cursor as well as Claude?
Yes. Once Omnisend 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 Omnisend once and every client picks it up.
What can an AI agent actually do with my Omnisend data?
It can look up and update contacts in Omnisend, add or remove tags, update many contacts at once, load new contacts as a batch, add and edit products and product categories, and list or set up campaigns. Because Omnisend has a lot of actions available, short concrete asks work best, such as "tag everyone from the Boston store as VIP" rather than a long paragraph.
Does connecting Omnisend give the AI everything in my account?
No. The agent works inside the access of the Omnisend account whose API key was used, and in Elaichi each person signs in as themselves, so every action is tied to a named person. Elaichi can narrow what the AI is allowed to do with Omnisend, for example read-only or contacts only, but it can never widen access beyond what the account already has.
Can I stop an agent from deleting or changing things in Omnisend?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Omnisend contacts and campaigns while blocking deletes or updates to products and categories. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it.
What happens to an Omnisend connection when someone leaves?
Offboarding that person in Elaichi ends their access to Omnisend through every client at once. If they set up a shared Omnisend connection, it keeps working for everyone else on the team. Disconnecting Omnisend once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Omnisend in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.