MCP · Hosted server

The marketing MCP server for your AI

Let Claude, Cursor, or any MCP client work inside your Spreeflo workspace — build segments, draft campaigns, and read your numbers without leaving the chat.

Connect your client

Works on every plan·One API key·Nothing to self-host

terminal
claude mcp add --transport http spreeflo https://mcp.spreeflo.com/mcp \
  --header "Authorization: Bearer <YOUR_API_KEY>"

Writes apply to your live workspace immediately — there's no approval queue here. Keep a human in the loop and check your client's confirmation settings first.

60+
tools exposed
0
servers to host
120
tool calls / minute
1
API key to connect

Why connect it

Your marketing stack, in the tool you're already thinking in

No copy-pasting CSVs into a chat window, no screenshots of dashboards. Your assistant reads the live workspace and does the work in it.

Ask in plain language

Describe the segment, the campaign, or the report you want. Your assistant translates it into the right tool calls and shows you what it did.

Reads your real data

Live audiences, contacts, tags, and performance numbers — answers come from the workspace itself, not from a stale export you pasted in.

Builds, not just advises

Segments, journeys, email and web push templates, and forms are all authorable over MCP. The output is a real draft in your workspace.

One key, one line

A hosted endpoint and a Spreeflo API key are the whole setup. Nothing to install, nothing to self-host, no OAuth flow to complete.

Dangerous actions removed

Deletes, campaign sends, and form publishes are refused by the server — not left to whether your client remembered to ask you first.

Your client does the thinking

Spreeflo exposes deterministic tools and nothing more. The model reasoning — and whatever it costs — stays with the client you already pay for.

Setup

Connected in about a minute

Two things: a Spreeflo API key, and one entry in your client.

Create an API key

In the Spreeflo app, go to Settings → API Keys and click + Add API Key. Name it after the client you're connecting, then copy it. It's the same key the REST API uses — there's no separate MCP credential.

Add the server to your client

Same endpoint everywhere — only the place your key goes changes. Pick your client:

ChatGPT

Connectors

Key in the URL

  1. 1.Turn on Developer mode in Settings → Connectors → Advanced.
  2. 2.Choose Add custom connector.
  3. 3.Paste the URL below, with your key as the last segment.
https://mcp.spreeflo.com/mcp/<YOUR_API_KEY>

Claude & Cursor

Desktop app, Cowork, Cursor

Header, or key in the URL

  1. 1.Cursor and other mcp.json clients: add the entry below.
  2. 2.Claude apps and Cowork: add a custom connector. Paste Bearer <key> under Request headers if you have that beta, otherwise use the URL form.
{
  "mcpServers": {
    "spreeflo": {
      "url": "https://mcp.spreeflo.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Claude Code

Terminal

Authorization header

  1. 1.Run the command below in your project.
  2. 2.Confirm with claude mcp list.
claude mcp add --transport http spreeflo https://mcp.spreeflo.com/mcp \
  --header "Authorization: Bearer <YOUR_API_KEY>"

Check it works

Ask for something small — "list my Spreeflo audiences". A working connection answers with your real audience names.

Full setup guide and troubleshooting

In practice

What it looks like to actually use

Two ordinary requests, and what your assistant does with the tools behind them.

Segment + campaign

Find everyone who opened something in the last 30 days but never clicked, and draft a re-engagement email for them.

Built the segment from your open and click events, then drafted the email against it:

  • list_audiences
  • create_segment
  • get_segment_preview
  • create_email_template

The segment and template are real drafts in your workspace. Sending stays in the app — MCP will not start a campaign.

Reporting

How did last month’s campaigns do, and which subject line worked best?

Pulled performance for every campaign in the window and compared them per template:

  • list_campaigns
  • get_campaign_performance
  • list_link_clicks

Read-only — the numbers come straight from your workspace, so there is nothing to export or reconcile.

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.

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.

Deleting anything Starting a campaign Resuming a campaign or journey Publishing a form
See the full tool catalog

Supercharge your marketing automation

14-day free trial
No commitment
Cancel anytime
FAQ

Questions, answered.