Give your agent a marketing stack

The Model Context Protocol is an open standard for connecting AI assistants to real tools and data. Instead of pasting exports into a chat window, your assistant calls a server directly — reading your live workspace and acting in it. Spreeflo runs a hosted MCP server, so there is nothing to install or self-host.

Any client that speaks remote MCP over Streamable HTTP — ChatGPT, Claude and Claude Cowork, Claude Code, Cursor, and others. Clients that can set an Authorization header use one; clients that only take a server URL put the key in the URL instead. Either way they reach the same tools with the same permissions.

Audiences and contacts, segments and tags, campaigns and journeys, email and web push templates, forms, and reporting. Your assistant can read all of it and create or edit most of it — the same capabilities you have in the app, on the same plan gates.

No. The riskiest actions are removed from the surface rather than left to your client settings: deletes, starting or resuming a campaign or journey, and publishing a form are refused by the server. Those stay in the app, where a person does them.

Not on this surface — a write applies to your live workspace the moment your assistant calls it. Whether you get asked first is entirely your client’s decision, so check its confirmation settings before you start. If you want a review step, use Spreeflo’s in-app AI, which queues changes as proposals instead.

Your connected client does all the model reasoning, so the model cost sits with that client rather than with Spreeflo. On our side the only governor is a rolling limit of roughly 120 tool calls per minute per workspace — there is no daily quota to wait out, and the window drains continuously.