Butter is now fully agentic: the Butter MCP is live.
Your posting pipeline, in one conversation. Connect your Butter workspace to Claude — or any MCP client — and tell your agent what you want in plain language. It uploads, organizes, assigns templates, routes posting methods, publishes, and reports back. Scoped to your own accounts, on the plan you already have.
Since day one, Butter's job has been to turn one content library into organic reach across every account you run. Until now, you drove that engine from the dashboard. Today there's a second way to drive it: an AI agent. The Butter MCP is a Model Context Protocol server that plugs your entire Butter workspace into Claude — so the work you used to click through, you can now just describe.
What "fully agentic" actually means
MCP (Model Context Protocol) is the open standard AI clients use to operate real software. The Butter MCP exposes over a hundred tools that cover the customer surface of Butter — content, folders, templates, captions, subtitles, account settings, posting schedules, publishing, and analytics. When you connect it, your agent isn't summarizing your dashboard; it's operating it.
Your agent runs the pipeline
Upload content, organize folders, assign templates, change account settings, schedule and publish — all from one conversation with Claude.
Four posting methods, routed per post type
API posting, your own phones, cloud phones, or manual. Your agent routes Reels one way and Stories another — in a single settings call.
Chains with your other connectors
Butter is a standard MCP connector. Add it next to your other tools and your agent chains them — a render finishes elsewhere, Butter distributes it.
Scoped, revocable, deliberate
OAuth-scoped to your own workspace with read and write scopes, revocable anytime — and publishing live always requires explicit confirmation.
One prompt, twelve tools
Here's the kind of instruction the Butter MCP is built for — one message, executed end-to-end:
"Drop the new renders into a fresh folder under @yourbrand, roll them out across all 50 accounts, assign 10 templates to each — split evenly. Post Reels through API posting and Stories from my own phones. Turn on autopilot, captions and covers, schedule between 9am and 11pm in my timezone, and send me a progress report against targets."
Behind that request the agent chains tools like these — the same operations you'd do by hand, just orchestrated for you:
butter_uploadbutter_create_folderbutter_assign_to_accountbutter_explore_templatesbutter_set_account_templatesbutter_generate_captionsbutter_set_api_posting_schedulebutter_post_nowbutter_client_insightsbutter_account_posting_progressBuilt for control, not chaos
Automation that can publish to real accounts has to be deliberate. The Butter MCP connects over OAuth with read and write scopes tied to your own workspace — nothing cross-tenant, and you can revoke the connection at any time. Publishing live is never a side effect: the posting tool requires an explicit confirmation before anything goes out. Your agent proposes; you stay in charge of what ships.
How to connect it
Add https://mcp.hellobutter.io/mcp as a custom connector in Claude, sign in with your Butter account, and approve the scopes.
That's the whole setup. The full walkthrough — including Claude Code, example prompts, and
how per-post-type routing works — is in our step-by-step guide,
and the Butter MCP page has live examples.
This is the direction Butter has been building toward: a data-backed organic engine you can delegate to. The dashboard isn't going anywhere — but now, neither is your agent.
Put an agent on your pipeline
The Butter MCP is included on every plan. Connect it in minutes — no new tier, no per-seat fee.