Omnisend MCP Server

Omnisend

Omnisend is eCommerce marketing automation: audience contacts first, then campaigns, abandoned carts, product catalog rows, and orders you create through the API.

Base URL is api.omnisend.com/v3 with an API key header. Reads use Pattern A — omit id to list with filters and pagination, pass id for one row.

Data model

• Contacts — identifiers (email, phone) each with channel status (subscribed, unsubscribed, nonSubscribed), tags, and custom properties.
• Campaigns — email sends with status and metrics; list reads are rate-limited (~1 req/s).
• Carts — abandoned-cart snapshots with line items and recovery URLs.
• Products — catalog rows with variants, images, and category ids.
• Orders — only orders created via POST /orders; store-synced Shopify (etc.) orders are not returned by the orders API.

Operational order

1. Audience — list or fetch contacts; filter by email, tag, segment, or subscription status before segmentation questions.
2. Campaign context — list or fetch campaigns when reviewing send performance or draft inventory.
3. Commerce signals — carts for abandonment, products for catalog checks, orders for API-ingested purchase events.
4. Writes — upsert contacts, carts, orders, or products with JSON bodies matching Omnisend field names; pass id on update. Delete carts, orders, products, or sent/draft campaigns when explicitly asked.

Gotchas

• Empty order history: When no API orders exist yet, listing orders may return a structured no-data outcome — not a credential failure. Store-synced orders never appear here.
• Contact identifiers: Two contacts cannot share the same email or phone; duplicate identifiers on create are ignored.
• Product replace: Updates use PUT and drop omitted fields — include full variant and image arrays when replacing.
• Campaign deletes: Only sent and draft campaigns can be deleted.