Marketing Cloud holds a lot of the numbers that matter for email: every send, every journey, every data extension your team built to feed them. Getting that into an analysis usually means a report export, a Tracking Extract or someone who knows SOAP. Salesforce Marketing Cloud Engagement is now a live MCP integration in Cogny, so an agent can pull send performance, journey email performance and the underlying data in the same conversation as your ads and analytics.

You connect it with an Installed Package, the same way you'd connect any server-side integration. There's no OAuth pop-up and no app for anyone to approve.

TL;DR

Salesforce Marketing Cloud is live now. Connect it from your workspace Settings → MCPs For Cogny.
12 read-only tools: get_account, list_email_sends, list_triggered_sends, get_triggered_send_summary, list_journeys, get_journey, list_entry_events, list_assets, get_asset, list_data_extensions, get_data_extension_fields, get_data_extension_rows. Nothing can be created, edited, sent, started or stopped.
Auth is a Server-to-Server API Integration from Installed Packages. Cogny exchanges its Client Id and Secret for a short-lived token on your own tenant (OAuth2 client credentials).
list_email_sends returns per-send sent / delivered / unique opens / unique clicks / bounces / unsubscribes, with the rates and window totals already calculated.
Journey emails are triggered sends, so they come from a different place. get_journey shows each email activity's triggered send key, and get_triggered_send_summary returns its lifetime performance.
The email-marketing scheduled template now recognises Marketing Cloud and knows which tools to call.
Available on any paid Cogny plan (Solo $9/mo and above).

What you can do with it

Tool	What Claude can do
`list_email_sends`	Per-send performance for user-initiated and scheduled sends in a date window, with open, click, click-to-open, bounce and unsubscribe rates plus totals
`list_triggered_sends` + `get_triggered_send_summary`	Every triggered/journey email definition, and lifetime sent, opens, clicks, opt-outs and not-sent reasons for up to 25 of them per call
`list_journeys` + `get_journey`	Journey Builder journeys with status, version and (optionally) population stats; one journey's entry source, goals, waits and email activities
`list_entry_events`	Journey entry events and the data extensions that feed them
`list_assets` + `get_asset`	Content Builder search by type, name or date; one email's subject line, preheader and (on request) HTML
`list_data_extensions` → `get_data_extension_fields` → `get_data_extension_rows`	Find a data extension, read its schema, then page through its rows with a filter

For example: "How did last month's newsletters perform against the month before — open and click rates per send?" "Which email in the welcome journey loses the most people, and what does its subject line say?" "What's in the Purchases data extension, and how many rows came in last week?"

The Send and TriggeredSendSummary objects are only available over Marketing Cloud's SOAP API. The connector makes those calls for you and hands the agent plain numbers.

How to connect it

In Marketing Cloud Engagement, open Setup → Platform Tools → Apps → Installed Packages and click New. Name it, e.g. "Cogny."
Add Component → API Integration → Server-to-Server.
Grant Read on Email, Saved Content, Journeys, Data Extensions and Tracking Events. Cogny never needs Write.
Save, then copy the Client Id, Client Secret and Authentication Base URI from the component.
In Cogny, go to Settings → MCPs For Cogny, click Connect on the Salesforce Marketing Cloud card and paste all three.

The package can only see the business unit it was installed in, unless you grant it access to others in the package settings.

How the connection works

The Client Id and Secret are stored encrypted and scoped to one workspace. On each call, the Cogny MCP proxy exchanges them for a token at https://<your-subdomain>.auth.marketingcloudapis.com/v2/token. It keeps that token until it expires (about 20 minutes), then sends it to your tenant's REST and SOAP endpoints. If the token response names an instance URL outside marketingcloudapis.com, the proxy ignores it.

On read-only trust

The integration is read-only by design. The only SOAP call it makes is Retrieve. The only REST POST is Content Builder's search endpoint, which reads and doesn't write. It has no tools to send an email, publish or stop a journey, or edit a data extension. Every tool carries MCP annotations marking it read-only, so Cogny's UI and any MCP client can see that before anything runs.

Data extension rows can contain subscriber data. get_data_extension_rows returns one page at a time, and its description asks the agent to fetch only the rows the analysis needs.

This integration came from a request through the "Wish for an MCP" card in Settings. If there's a platform you want next, ask there. Connect Marketing Cloud from your Cogny dashboard and ask your first question.