MCP · Anthropic
Marketing MCP for Claude Cowork
Give Cowork your Spreeflo workspace and it can build segments, draft campaigns, and pull performance while it works alongside your other tools.
Runs on web, desktop and mobile·Connects from Anthropic’s cloud·No local install
https://mcp.spreeflo.com/mcp/<YOUR_API_KEY>Writes apply to your live workspace immediately — there's no approval queue here. Keep a human in the loop and check Claude Cowork's confirmation settings first.
The agent
What is Claude Cowork?
Claude Cowork is Anthropic’s agentic workspace — Claude working through multi-step tasks with your files and connected apps rather than answering one message at a time. Custom connectors let it reach remote MCP servers, which is how it reaches Spreeflo.
Cloud-side connection
Cowork dials your MCP server from Anthropic’s infrastructure, not your laptop — so the connection keeps working when your machine is asleep.
Multi-step autonomy
It chains tool calls on its own, so “segment these people then draft them an email” is one request rather than four.
Alongside your other tools
Spreeflo sits next to whatever else you have connected, so your marketing data can meet the rest of your work in one task.
Setup
Connect Claude Cowork in about a minute
A Spreeflo API key, and one entry in Claude Cowork.
Create an API key
In the Spreeflo app, go to Settings → API Keys and click + Add API Key. Name it Claude Cowork so you can revoke this one connection later without touching the others.
Add the Spreeflo MCP server
Connector dialog- 1.Open Customize → Connectors and choose Add custom connector.
- 2.Paste the URL below, with your Spreeflo API key as the last segment.
- 3.If your account has the Request headers beta, instead use the plain
/mcpendpoint and storeBearer <key>as theauthorizationheader — the key then never sits in a URL.
https://mcp.spreeflo.com/mcp/<YOUR_API_KEY>Request header authentication is in beta and rolling out gradually, which is why the URL form is the default here.
Check it works
Ask Claude Cowork for something small — "list my Spreeflo audiences". A working connection is one where the connector returns your real audience names rather than an auth error.
Full setup guide and troubleshootingIn practice
What Claude Cowork does with it
Two ordinary requests, and the Spreeflo tools behind them.
Pull last week’s campaign numbers and tell me which segment is going cold.
Compared performance across the window, then previewed the segments behind the weakest results:
list_campaignsget_campaign_performancelist_segmentsget_segment_preview
All reads — nothing in the workspace changed.
Take the positioning doc I shared and draft a re-engagement email in our voice.
Read the brief, checked your business profile for tone, and saved a draft template:
get_business_profileread_format_doccreate_email_template
Saved as a draft. Publishing and sending stay in the Spreeflo app.
Running it
What changes when the connection is cloud-side
Cowork does not proxy through your laptop — Anthropic’s infrastructure holds the connector and calls Spreeflo directly. That is what makes it convenient, and it is also what makes these four things worth knowing.
Your key is stored with the connector
Because the call originates in Anthropic’s cloud rather than on your machine, the credential lives with the connector configuration. Treat it the way you would any key handed to a third-party service: dedicated to Cowork, and rotated on the same schedule as the rest.
Key-in-URL is the fallback, not the goal
Where the request-headers beta has reached your account, put the key in an authorization header instead. URLs are the thing most likely to end up pasted into a ticket or a screenshot, and a key in the path travels with them.
One request can become many writes
Cowork chains tool calls without checking back, so “clean up the segments and redraft the welcome email” may touch a dozen objects before it reports. Its confirmation settings are the place to slow that down — Spreeflo applies each call as it arrives.
When the connector will not add
A connector that fails at the point of adding is nearly always a malformed URL rather than a rejected key — a missing path segment, or a trailing slash before the key. Re-paste the endpoint exactly as shown above before regenerating anything.
It keeps working when you are not there
A cloud-side connector does not need your machine awake, which is genuinely useful and easy to forget. A long task you kicked off and closed the tab on carries on running against your live workspace. If you want a hard stop, revoking the Spreeflo key is the switch that works immediately — closing the app is not.
Why this pairing
Claude Cowork + Spreeflo
- Connects without installing anything locally
- Reaches Spreeflo alongside your files and other connectors
- Chains multiple Spreeflo tools in one request
- Header auth available where the beta has landed
- Irreversible actions refused server-side, not left to settings
Coverage
Everything it can touch
The same surfaces you work with in the app, exposed as tools — and a short list that is deliberately off limits.
Cowork usually spans the widest slice of this in a single task, since it chains calls — reading performance, then acting on what it found, without stopping to ask in between.
Audience
- Audiences and contacts
- Segments, static and dynamic
- Tags
- Custom contact attributes
- CSV import
Sending
- Campaigns and journeys
- Email templates
- Web push templates
- Sender and domain identities
Capture
- Forms and question types
- Inline and popup embeds
- Response summaries
- CSV export of responses
Insight
- Campaign and web push performance
- Tracked events and pages
- Link clicks
- Form analytics
What MCP refuses to do
These are irreversible or they reach real people, so they are removed from the surface rather than left to your client's confirmation settings. A person does them in the app.