Connect your AI client

This guide connects your AI client to Spreeflo's hosted MCP server. You add the server to your client, then sign in to Spreeflo and approve the connection — there's no key to create or paste.

Step 1: Add the server to your client

The server endpoint is:

https://mcp.spreeflo.com/mcp

Claude, Cowork, and ChatGPT

In claude.ai, the Claude desktop app, or Claude Cowork, open Settings > Connectors and choose Add custom connector. Paste the endpoint above as the URL and connect. Leave any client ID and secret fields empty — Spreeflo registers the client for you.

In ChatGPT, turn on Developer mode under Settings > Connectors > Advanced, then add a custom connector with the endpoint above and OAuth as the authentication method.

Cursor and other mcp.json clients

Add a spreeflo entry to your client's MCP configuration file, then use the sign-in prompt your client shows next to it:

{
  "mcpServers": {
    "spreeflo": {
      "url": "https://mcp.spreeflo.com/mcp"
    }
  }
}

Claude Code

Run this in your terminal:

claude mcp add --transport http spreeflo https://mcp.spreeflo.com/mcp

Then start Claude Code, run /mcp, pick spreeflo and choose Authenticate.

Step 2: Sign in and approve

Your client opens Spreeflo in your browser. Sign in the way you normally do — email and password, or Google — and you'll see an approval screen naming the app that's asking to connect:

Click Approve and your browser hands you back to the client. The approval screen is valid for 15 minutes — if it expires, start the connection again from your client.

Warning: Only approve a connection you started yourself, from an app you recognise. The approval screen shows which app is asking and where you'll be sent back to — if either looks wrong, click Cancel.

Step 3: Verify the connection

Ask your client to list the Spreeflo tools it can see, or try a simple read such as "list my Spreeflo audiences".

A working connection returns your actual workspace data — your audience names, your campaigns. If your client shows a tool list, you should see Spreeflo tools such as list_campaigns, get_segment_preview, and — if you ticked Make changes — create_email_template. If something goes wrong instead, see Troubleshooting below.

Headless agents and automation

Signing in needs a browser. For an agent that runs somewhere it can't open one — a server, a container, a scheduled job — use a Spreeflo API key instead. In the Spreeflo app, go to Settings > API keys, click Create API key, and name it after the agent. It's the same kind of key the Spreeflo REST API uses.

Send it in the Authorization header, and only there — a key placed in the server URL is rejected:

{
  "mcpServers": {
    "spreeflo": {
      "url": "https://mcp.spreeflo.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Warning: An API key can read and change its workspace — everything its owner's role allows. Give each agent its own key, load it from an environment variable or secret store rather than a committed file, and never put it in the server URL — URLs end up in logs, browser history and screenshots.

What the connection can reach

Check your client's confirmation settings

Before you start working, check how your client handles tools that modify data. Spreeflo annotates every tool so a well-behaved client can tell reads from writes, but Spreeflo will never prompt you — the decision to ask you before running a write belongs entirely to your client.

Warning: Writes apply immediately to your live workspace. There is no staging step, no pending list, and no approval queue on this surface. If you want to review changes before they land, use Spreeflo's in-app AI instead, or approve the connection without Make changes.

The riskiest actions are removed rather than left to your client's settings: deleting anything, starting or resuming a campaign or journey, sending or scheduling a broadcast, and publishing a form are not available over MCP — a person does them in the Spreeflo app.

Troubleshooting

Disconnecting an AI app

You can disconnect a signed-in AI app from either side:

To cut off every connection a person made at once, remove them from the workspace, or switch the AI agent off in the team's settings.

For a headless agent, revoke its API key in Settings > API keys. Once revoked, a key can't be reactivated — create a new one and update the agent's configuration.

Need Immediate Help? Contact our support team at support@spreeflo.com or check our other guides for more information.