MCP · Perplexity
Marketing MCP for Perplexity Computer
Computer researches the web and acts on what it finds. Connect Spreeflo and the research can land as a segment, a draft, or a report in your workspace.
Pro, Max and Enterprise·Sign in with OAuth·Custom remote connector
https://mcp.spreeflo.com/mcpWrites apply to your live workspace immediately — there's no approval queue here. Keep a human in the loop and check Perplexity Computer's confirmation settings first.
The agent
What is Perplexity Computer?
Perplexity Computer is Perplexity’s autonomous agent — multi-step tasks with memory, file access, and live web access. Custom remote connectors take an MCP server URL and an auth choice, which is all Spreeflo needs.
Research-first
It brings live web context to the task, so market or competitor findings can turn straight into audience work.
Auth your way
Custom connectors let you pick OAuth, an API key, or open authentication — OAuth is the one to pick for Spreeflo: you sign in and approve, and no key is pasted anywhere.
Repeatable workflows
Tasks it does well can be kept and re-run, so a weekly marketing report stops being something you assemble by hand.
Setup
Connect Perplexity Computer in about a minute
One entry in Perplexity Computer, then sign in to Spreeflo. No key to create or paste.
Add the Spreeflo MCP server
Custom connector- 1.Open connector settings and choose to add a custom remote connector.
- 2.Enter the Spreeflo MCP server URL.
- 3.Pick OAuth auth, then sign in to Spreeflo, choose the workspace, and approve.
https://mcp.spreeflo.com/mcpCustom remote connectors require a Pro, Max or Enterprise plan on Perplexity’s side.
Sign in and approve
Spreeflo opens in your browser. Sign in, pick the workspace Perplexity Computer should reach, and click Approve. Tick Make changes if it should be able to write — leave it off for a read-only connection.
Check it works
Ask Perplexity Computer for something small — "list my Spreeflo audiences". A working connection is one where the connector answers from your workspace rather than from the web.
Full setup guide and troubleshootingIn practice
What Perplexity Computer does with it
Two ordinary requests, and the Spreeflo tools behind them.
Find what our competitors changed in pricing this quarter, then segment customers likely to care.
Researched the changes, then built an audience from the attributes that matched:
list_contact_attributescreate_segmentget_segment_preview
The web research is Perplexity’s; the segment is a real saved segment in Spreeflo.
Put together this week’s marketing report — sends, opens, clicks, and what moved.
Pulled the numbers across campaigns and web push, and the links people actually clicked:
get_campaign_performanceget_webpush_performancelist_link_clicks
Read-only, so it is safe to schedule as a recurring task.
Running it
Where research stops and your workspace begins
Computer is the only client here that brings outside information into the task. That is the whole appeal, and it also means the boundary between what it read on the web and what it writes to your contacts deserves more attention than it would with a local agent.
Web findings are not verified facts
A competitor’s pricing page read this morning is a good input to a segment definition. It is a poor thing to write into contact attributes as though it were first-party data. Let research shape the query, and keep what lands in the workspace to things your own events and attributes can support.
Recurring tasks are best kept read-only
Saved workflows are the strongest reason to pair these two — a marketing report that assembles itself weekly costs nothing to keep. Reporting tools are all reads, so a schedule cannot compound a mistake. A recurring task that writes is a different risk profile entirely.
OAuth, and approve it read-only for reports
Pick OAuth when you add the connector. Spreeflo’s approval screen then asks whether Computer may make changes — for a connector that exists to run recurring reports, leave that unticked and Computer is offered only the tools that read. Open auth will not work: Spreeflo has no unauthenticated mode.
The connector is plan-gated
Custom remote connectors need Pro, Max or Enterprise on Perplexity’s side. That is Perplexity’s gate rather than Spreeflo’s — every Spreeflo plan that includes API access can serve the connection, so if the option is missing it is the subscription tier to check first.
Research quality is not workspace quality
It is tempting to treat a well-sourced answer as a well-founded segment. They are different claims: one is about the world, the other is about who is in your audience. Preview a segment before you act on it — get_segment_preview shows you the actual contacts — rather than trusting that a confident narrative produced a sensible query.
Why this pairing
Perplexity Computer + Spreeflo
- Live web research feeding real audience work
- Signs in with OAuth — no key to paste or rotate
- Recurring tasks turn reports into something automatic
- Reads reflect the workspace, not a stale export
- No MCP tool for sends, deletes or publishes
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.
Computer leans on the insight column hardest — performance, clicks and events pulled into a report — with segment work as the place its research actually lands.
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 can’t 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.
Supercharge your marketing automation
FAQ
Questions, answered.
Pro, Max and Enterprise. The restriction is on Perplexity’s side and applies to custom remote connectors generally, not to Spreeflo in particular. Nothing on the Spreeflo end differs by their plan tier — the same tools and the same rate limit apply once the connector is added.
Only what it explicitly writes through a tool call. Research itself touches nothing. But a segment or a contact attribute it creates off the back of that research is a real, persistent object, so the meaningful review point is the write, not the browsing.
Yes — that is the pairing at its best. Campaign performance, web push numbers and link clicks are all read-only tools, so a saved recurring task can assemble the report on a schedule without any risk of it changing something while you are not looking.
No. Spreeflo runs a hosted MCP server, so Perplexity Computer calls it directly over Streamable HTTP — nothing to install, nothing to self-host, no SDK to keep up to date. A server URL and a sign-in (or, for a headless agent, an API key in the Authorization header) are the whole integration.
It cannot delete anything or start a send. Spreeflo has no MCP tool for deletes, starting or resuming a campaign or journey, sending or scheduling a broadcast, or publishing a form, rather than leaving them to client settings. Those stay in the Spreeflo app, where a person does them. Journeys you have already switched on keep running, though, so editing a contact, its tags, a segment or an email template, or importing contacts, can set one off, just as the same edit would in the app.
The key resolves to exactly one workspace, and every action runs as the person who owns that key — their membership re-verified on each request. The audit trail names a real person, so agent-made changes are attributable.