Access, auth, and limits
The Omnisend MCP server lives at https://mcp.omnisend.com/mcp and authenticates over OAuth, not a pasted API key. When you add the connector you are redirected to Omnisend's authorization flow, log in, and approve the requested permissions, which means an Admin-level account is required to connect. That OAuth handshake is the right call for a server that can create campaigns and edit segments, since it scopes access to an approved grant instead of a long-lived static key.
Setup is per-client. In ChatGPT you add the published Omnisend app from the app directory; in Claude you currently add it under Settings, Connectors, Add custom connector, name it Omnisend and paste the server URL, then complete the OAuth login. Omnisend has flagged an official one-click Claude connector as coming soon, so the custom-connector step is a temporary bridge. There is no separate MCP price tier: MCP access rides on your existing Omnisend plan (the same free-to-start account that runs your campaigns), and it is bounded by whatever your account can already do.
Where it works and what to build
Supported clients today are ChatGPT (via a published app in the ChatGPT app directory) and Claude (Web and Desktop, added as a custom connector until the official one lands). Both connect to the same hosted server over OAuth. Omnisend is explicit that you should point an advanced or thinking model at it: a fast model will give incomplete or inaccurate answers because the server exposes real, consequential actions rather than read-only lookups.
Real workflows worth running once it is connected: ask the assistant to build an abandoned-cart or welcome flow and it drafts the automation in your account; ask which campaigns drove the most revenue last month and it pulls the reporting and breaks revenue down by campaign and automation; ask it to audit your automations and it flags the flows you are missing; ask for a segment of lapsed high-value buyers and it recommends the rules and can create the segment. It will also critique subject lines against your own historical send data instead of generic best practice. The through-line is that Omnisend owns the deliverability and data layer, and the MCP lets an agent operate that layer conversationally.
Which AI clients can use Omnisend MCP?
Not every AI assistant supports MCP natively. Per-client picture for Omnisend:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Via connectors | Add as a custom connector (Settings, Connectors) pointing at mcp.omnisend.com/mcp, then OAuth login. Official one-click connector coming soon. |
| ChatGPT | Native MCP | Published Omnisend app in the ChatGPT app directory; connects over OAuth. |
How to connect Omnisend MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"omnisend": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.omnisend.com/mcp
// Claude Code (one-liner): claude mcp add omnisend <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.omnisend.com/mcp.
Does Omnisend MCP cost extra?
Omnisend ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Omnisend plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Omnisend also publishes a REST API
Omnisend publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Omnisend from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What campaigns underperformed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Omnisend data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Omnisend account
- Multi-account workflows without context-switching the Omnisend UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Omnisend data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Omnisend safe
Limits and gotchas
- Official MCP server — published by Omnisend themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (api_key). Expect to configure that on first install.
- Rate limits: MCP calls count against your underlying Omnisend API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Score: 7/10 on MCP-readiness. Omnisend ships a genuine first-party hosted MCP server (mcp.omnisend.com/mcp) with OAuth auth and read-plus-write reach across campaigns, segments, automations, and reporting, available from both Claude and ChatGPT. That is a strong, native agent path for an ecommerce email and SMS platform. It falls short of the 8s (HubSpot, GoHighLevel) because the one-click Claude connector is still coming soon (Claude users wire it as a custom connector for now), there are no official API SDKs behind it, and Omnisend publishes no tool count or structured-output guarantees, so deeper agent work leans on the REST API.
Solid agent fit with a first-party MCP server and a clean REST API. Omnisend hosts an official MCP server at mcp.omnisend.com/mcp, authenticated over OAuth, so an agent can create campaigns, build automations, recommend and edit segments, and pull revenue reporting from Claude or ChatGPT. The REST API (api.omnisend.com/api) is date-versioned via an Omnisend-Version header, uses cursor pagination and RFC 9457 error bodies, and spans contacts, events, products, campaigns, segments, automations, and reports. It sits below the GA-official tier because the one-click Claude connector is still coming soon (custom connector for now), there are no official SDKs, and webhooks are an automation-workflow action rather than a subscription API.
Scored by Joonas (TMB).
Omnisend MCP & API FAQ
Is the Omnisend MCP server official?+
Can I use the Omnisend MCP with Cursor or Codex?+
Does Omnisend have a public API?+
Sources
- Omnisend official site: https://www.omnisend.com/
- MCP server page: https://mcp.omnisend.com/mcp
- API docs: https://api-docs.omnisend.com/
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.