Omnisend Is Live in Cogny: Read Email & SMS Marketing Performance and Draft Campaigns from an Agent
If your store's email and SMS marketing runs on Omnisend, that's where your customer relationships live — the segments, the automations, the campaigns that bring people back. Until today none of it was reachable from a Cogny agent. Now it is: Omnisend is a live MCP integration in the email catalog alongside Klaviyo, Mailchimp, beehiiv, Brevo and the rest.
No OAuth dance and no developer app: one API key created in Omnisend in about a minute, pasted once into Settings → Cogny Managed MCPs, and your agent is in.
TL;DR
- Omnisend is live now. Connect it with an API key from your warehouse Settings → Cogny Managed MCPs.
- 32 tools across contacts, tags, segments, campaigns, automations, forms, products and email templates. The read tools cover contacts with filters, segment statistics, campaign performance and UTM settings, automation and form lists, your product catalogue, and email template content.
- Campaigns are always drafts.
create_campaignsaves a new email campaign as a draft only — nothing is scheduled or sent to your audience until you callsend_campaignwith confirmation. - Writes are confirm-gated. Every tool that sends or changes your audience —
send_campaign(sends to your real audience),send_campaign_test_email(sends a test),enable_automation(turns a draft automation live), and the contact, tag and segment writes (upsert_contact,update_contact,add_contact_tags,remove_contact_tags,create_segment,update_segment) — describes what it would do and makes no call to Omnisend until you approve withconfirm=true. - The Email Marketing Optimization scheduled template now recognizes Omnisend alongside the rest of the email catalog.
- Works from any MCP client on
app.cogny.com/mcp. - Included in Solo ($9/mo); bring your own agent and the standard MCP tools run under fair use.
What you can do with it
| Area | What Claude can do |
|---|---|
| Contacts | List contacts with email, phone or tag filters (list_contacts), look one up by email (get_contact), create or update a contact by email (upsert_contact) or by id (update_contact), and batch-add or batch-remove tags (add_contact_tags / remove_contact_tags) |
| Segments | List segments (list_segments), read a segment's size and stats (get_segment_statistics), and create or update dynamic segments (create_segment / update_segment) |
| Campaigns | List campaigns (list_campaigns), read one and its performance report (get_campaign / get_campaign_report), read and set UTM parameters (get_campaign_utm / update_campaign_utm), build a campaign as a draft (create_campaign / update_campaign), copy one (copy_campaign), and — with your confirmation — test-send or send it (send_campaign_test_email / send_campaign) or cancel a scheduled send (cancel_campaign) |
| Automations | List automations and read one (list_automations / get_automation), copy one (copy_automation), and — with your confirmation — enable or disable a flow (enable_automation / disable_automation) |
| Forms & products | List signup forms and read a form's performance (list_forms / get_form_report), and browse your product catalogue (list_products / get_product) |
| Templates | List email templates and read a template's content (list_email_templates / get_email_content) |
In plain terms: "Which of our last ten email campaigns got the most clicks per open?" "How is the 'engaged last 30 days' segment performing?" "What tags are on the people who abandoned a cart?" "Draft a campaign announcing next week's sale — don't send it, just save it." The answers — and the drafts — happen against Omnisend's own API, not a spreadsheet.
Writes stay narrow on purpose
The first release is deliberately limited to the safe, reversible moves:
- Drafts only, never sends.
create_campaignandupdate_campaignwork on drafts. Nothing is scheduled or sent to your audience until you explicitly callsend_campaignwithconfirm=true.send_campaign_test_emailsends only to email addresses you name — never to your real audience. - Writes are confirm-gated. Every tool that sends or changes your audience —
send_campaign(sends to your actual audience),send_campaign_test_email(sends a test),enable_automation(turns a draft automation live so it can email and text real contacts), and the contact, tag and segment writes (upsert_contact,update_contact,add_contact_tags,remove_contact_tags,create_segment,update_segment) — first describes exactly what it would do, and makes no call to Omnisend until you approve withconfirm=true. Nothing goes out and no audience changes without your say-so. - Campaign cancelling is the one destructive move.
cancel_campaignstops a scheduled or in-flight send and carries the destructive annotation, so the UI flags it before it runs.
There are no delete tools for contacts, campaigns or segments — the agent can build, update and even send, but it can't tear anything down or delete records from Omnisend.
Reading is read-only, and honest about it
The read tools are genuinely read-only. Every tool carries MCP behavior annotations, so Cogny's UI and Claude.ai connectors know which ones read and which write, and which ones can send to your audience. Omnisend rate-limits most endpoints at 400 requests per minute (segment writes tighter, at 15 per minute) — on a 429 the integration names the limit clearly instead of guessing.
How to connect it
- In Omnisend, open Integrations → API Keys and click Create API Key. Copy the key — it is only shown once.
- In your warehouse Settings → Cogny Managed MCPs, click Connect on the Omnisend card and paste the API key.
The credential is stored encrypted and sent only to Omnisend's API. Disconnect any time with one click, and revoke the key back in Omnisend's Integrations → API Keys screen if you ever stop using Cogny.
If you run email and SMS marketing on Omnisend, this is the connector that puts your contacts, segments, campaigns and automations one prompt away — with the safety rail that a campaign is a draft until you decide to send it. Connect it from your Cogny dashboard and ask your first question.