MCP · nanoco.ai
Marketing MCP for NanoClaw
NanoClaw keeps every agent in its own container. Connect Spreeflo and your marketing tools are reachable without handing the agent your whole machine.
Container-isolated·Open source·Built on Anthropic’s Agents SDK
{
"mcpServers": {
"spreeflo": {
"url": "https://mcp.spreeflo.com/mcp",
"headers": { "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 NanoClaw's confirmation settings first.
The agent
What is NanoClaw?
NanoClaw is a lightweight, security-focused agent runtime — a smaller, auditable alternative to OpenClaw that runs each agent inside its own container on Anthropic’s Agents SDK. Agent templates can carry MCP tools, which is how Spreeflo gets in.
Isolation by default
Each agent runs in its own container, so a marketing agent’s reach ends at the tools you gave it.
Templated agents
Instructions plus MCP tools can be stamped from a reusable bundle — a “marketing agent” becomes repeatable.
Stays local
Messages, files and keys remain on your machine, which matters when the tools can write to your workspace.
Setup
Connect NanoClaw in about a minute
A Spreeflo API key, and one entry in NanoClaw.
Create an API key
In the Spreeflo app, go to Settings → API Keys and click + Add API Key. Name it NanoClaw so you can revoke this one connection later without touching the others.
Add the Spreeflo MCP server
Agent template- 1.Add Spreeflo as an MCP tool on the agent template you want to give marketing access.
- 2.Use the Streamable HTTP form below, with the key in the
Authorizationheader. - 3.Stamp or restart the agent so it picks up the new tools.
{
"mcpServers": {
"spreeflo": {
"url": "https://mcp.spreeflo.com/mcp",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Give the marketing agent its own Spreeflo key so you can revoke it without touching your other agents.
Check it works
Ask NanoClaw for something small — "list my Spreeflo audiences". A working connection is one where your real audience names come back inside the container.
Full setup guide and troubleshootingIn practice
What NanoClaw does with it
Two ordinary requests, and the Spreeflo tools behind them.
You handle our newsletter. Draft this month’s issue from the blog posts I dropped in.
Read the posts, checked your tone settings, and saved the draft:
get_business_profileread_format_doccreate_email_template
The container only has the Spreeflo tools you granted — nothing else on your machine.
Tag everyone who filled the pricing form this quarter so we can follow up.
Found the responses and tagged the contacts behind them:
get_form_summarylist_tagstag_contacts
A real write — worth checking your confirmation settings before you let it run unattended.
Running it
What the container does and does not cover
NanoClaw’s isolation is about your machine. Spreeflo sits on the other side of the network boundary, so the container and the API key protect different things — worth being precise about which is which before you stamp an agent.
The container bounds the host, not the workspace
Isolation stops a marketing agent reading your home directory or your SSH keys. It does not narrow what the Spreeflo key can do — inside the container, that key reaches your whole workspace exactly as it would anywhere else. Two separate boundaries, and only one of them is NanoClaw’s.
Templates share the key they were stamped with
A template is the unit of reuse, so every agent stamped from it carries the same Spreeflo credential. That is convenient until you want to cut one agent off: revoking the key stops all of them. If you need them revocable apart, give each template its own key rather than each container.
The container still needs egress
Spreeflo is a hosted server, not a local process, so the agent needs outbound HTTPS to mcp.spreeflo.com. A container hardened to no network at all will start cleanly and simply show no Spreeflo tools — the usual symptom of an egress rule rather than a bad key.
Tearing down the container changes nothing here
Rebuilding or discarding an agent resets its local state only. Segments it created, templates it drafted and tags it applied are already in your workspace and stay there — the disposability is on NanoClaw’s side of the line, not Spreeflo’s.
Container isolation is not an approval step
It is easy to read “sandboxed” as “safe to leave alone”. A contained agent still writes to your live workspace the moment it calls a tool, and NanoClaw will not hold that write for you. Isolation limits blast radius on your machine; for the workspace, the controls that matter are the agent’s own confirmation settings and the actions Spreeflo refuses outright.
Why this pairing
NanoClaw + Spreeflo
- Per-agent containers limit what a marketing agent can touch
- Templates make a scoped marketing agent repeatable
- Keys and files stay on your machine
- One Spreeflo key per agent, revocable independently
- Deletes, sends and publishes refused server-side
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.
A scoped NanoClaw agent usually lives in one corner of this — templates and forms for a newsletter agent, tags and segments for a cleanup one. The key still reaches all of it, which is the argument for one template per job.
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.