Skip to content

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.

1

In Elaichi

Connect Omnisend once

  1. Open Connections, choose Add connection, and pick Omnisend.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

omnisend
Omnisend
Attentive
Beamer
beehiiv
Bird
Buffer
2

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.

Omnisend MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Omnisend MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Omnisend MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.”

See all 82 Omnisend tools below

Compare

Elaichi vs Zapier MCP vs Composio for Omnisend

All three can connect Omnisend to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Omnisend, by what to check
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 Omnisend tools Allow or restrict single Omnisend 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 Omnisend 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

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

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
ElaichiTools
Tool Action Description
List all Omnisend contacts List List Omnisend contacts with optional filters by email, phone, status, segment, tag, or update date. Returns: id, email, firstName, lastName, gender, birthdate, address, city, state, country, countryCode, postalCode, status, tags, identifiers, consents, optIns, statuses, phone, segments, customProperties, trackingConsents, createdAt, updatedAt. tag and status are mutually exclusive.
Create a Omnisend contact Create Create a new Omnisend contact, or update an existing one if the email identifier already matches. Returns: id, createdAt, updatedAt, name, conditionGroups.
Get single Omnisend contact by ID Get Get a single Omnisend contact by id. Returns: id, email, firstName, lastName, gender, birthdate, address, city, state, country, countryCode, postalCode, status, tags, identifiers, consents, optIns, statuses, phone, segments, customProperties, trackingConsents, createdAt, updatedAt. Required: id.
Update a Omnisend contact by ID Update Update an Omnisend contact by id. Returns: id, email, firstName, lastName, gender, birthdate, address, city, state, country, countryCode, postalCode, status, tags, identifiers, consents, optIns, statuses, phone, segments, customProperties, trackingConsents, createdAt, updatedAt. Required: id.
Omnisend contacts add tags Add Batch add tags to Omnisend contacts by contact IDs, emails, phone numbers, or segment. Tagging is asynchronous so tags may not appear immediately. Returns an empty 202 response on success. Required: tags. At least one of contactIDs, emails, phones, or segmentID must also be provided.

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
ElaichiToolboxes
Name Source template Tools Created

Lifecycle Marketing toolbox

Omnisend · contacts and tags

Omnisend starter 18 Mar 4, 2026

Ecommerce toolbox

Omnisend · products and catalog

— 9 Mar 2, 2026

Customer Support toolbox

Omnisend · contact lookups

— 24 Feb 27, 2026

Growth toolbox

Omnisend · contact segments

Omnisend starter 6 Feb 19, 2026

Analytics toolbox

Omnisend · contact and product reporting

— 31 Jan 30, 2026

Brand Operations toolbox

Omnisend · brand settings

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
OM

Omnisend (Lifecycle EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
OM

Omnisend (Retail US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
OM

Omnisend (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
OM

Omnisend (Growth)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
OM

Omnisend (Wholesale)

Connected by Ryan Hayes

Personal • Active Not shared
OM

Omnisend (Brand HQ)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Omnisend Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Omnisend Contacts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Omnisend Contacts List Toolbox

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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch contacts

    Omnisend

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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 my team share one Omnisend connection?

Yes. One person connects Omnisend in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names who updated a contact or created a campaign in Omnisend.

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.

Does the Omnisend MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Omnisend 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 Omnisend?

Yes. Both let Claude, ChatGPT or Cursor use Omnisend. 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 Omnisend call.

How is Elaichi different from Composio for Omnisend?

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 Omnisend: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Omnisend in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.