API posting
apiPublish automatically through Butter’s API integration.
Hands-off scheduled publishing on the hours you set — and the one method your agent can also fire on demand.
Butter MCP connects your workspace to Claude and any MCP client. Tell your agent what you want in plain language — it changes settings, routes each post type to API posting, your own phones, cloud phones or manual, assigns templates, publishes and reports back, all scoped to your own accounts.
Whenever a fresh video finishes rendering in Higgsfield, drop it into @yourbrand under a new folder, then roll it out across all 50 of @yourbrand’s accounts. Assign 10 templates to each — split evenly — and set repurpose strength anywhere from 1 to 5. Post Reels through the API and Stories from my own iPhones and Androids. Turn on autopilot, text overlays, captions, and cover photos, and schedule everything at random times between 9am and 11pm in my timezone. Once it’s live, send me a report so I know we’re on pace to hit our targets.
Done — each new Higgsfield render lands in a fresh folder on @yourbrand, fans out across all 50 accounts with 10 templates each split evenly, repurpose strength dialed in, Reels on API posting and Stories on your own iPhones and Androids, autopilot, text overlays, captions and covers on, and a random 9am–11pm window in your timezone — capped with a progress report against your targets.
Higgsfield is a separate MCP connector. With both it and Butter added to Claude, your agent chains them — Butter never reaches into Higgsfield itself.
Butter can publish through its API integration, from your own phones, from cloud phones, or leave it to you. Your agent routes each post type independently — reels one way, stories another — in a single settings call.
butter_update_account_settings reel_post_method · story_post_method · carousel_post_methodapiPublish automatically through Butter’s API integration.
Hands-off scheduled publishing on the hours you set — and the one method your agent can also fire on demand.
my_phonesPost from your own physical phones.
Control your own devices — content goes out from real handsets you’ve connected and manage yourself.
geelarkPost via managed cloud phones.
Fully cloud-hosted devices post on your behalf — no hardware for you to run.
manualYou post it yourself.
Butter renders and queues the content; you publish it on your own time.
A method is only offered where it’s connected and capable — carousels post via API or manual, and API stories are Instagram-only. Your agent respects the same rules the dashboard does.
Feed in raw clips — uploaded, rendered in Higgsfield, from anywhere — and Butter’s generation engine turns them into a steady stream of on-brand variants automatically, any vibe. Two paths, both driven from the connector.
Automatic clip transforms at a strength you set.
Dial repurpose strength from 1–5 and Butter reshapes each source clip into distinct variants — no editing, no templates required.
butter_set_repurposer_configbutter_update_account_settingsStyled editor-template variants, on brand.
Assign editor templates and Butter renders your content through them — then tune the caption and cover mix so every variant fits the account.
butter_explore_templatesbutter_set_account_templatesbutter_set_caption_weightsbutter_set_cover_weightsTrending audio and AI overlays are applied automatically by Butter’s generation engine from an admin-curated pool — there’s no per-account toggle to manage.
You describe the outcome in plain language; the agent chains the right tools, stays scoped to your own accounts, and reports exactly what happened. Tap through a few real ones:
"Post @youraccount’s reels via API, its stories from My Phones, and carousels manually."
butter_list_accounts butter_get_account butter_update_account_settings Resolves @youraccount to its id, reads the current settings, then sets reel_post_method, story_post_method and carousel_post_method in one call — three post types, three different methods. Nothing else is touched.
No admin powers, no other tenant's data — every tool acts as your Butter user and only touches your own clients and accounts. Browse, configure, route, publish, template, tune and report from the hosted connector; the local CLI adds bulk upload and assignment.
Resolve a client or account by name to its id and read its full current state — the first step before any change.
butter_list_clientsbutter_list_accountsbutter_get_accountPosting goals per type, auto-generate, auto-sync, autopilot (+%), captions, organic-post tracking, bio, cross-promo & tracking link, marketing cost — set only what you name; the rest is left as-is.
butter_update_account_settingsbutter_set_timezonebutter_set_api_posting_scheduleRoute reels, stories and carousels each to API posting, My Phones, Cloud Phones or manual — independently, in a single settings call.
butter_update_account_settingsGet the browser link to connect an account, check the live connection, see how many rendered items are ready, and publish one now.
butter_api_connectbutter_api_statusbutter_api_ready_countbutter_api_post_nowBrowse your own templates and the public Explore gallery, inspect one, then set which templates an account generates from — foreign templates auto-clone into your client.
butter_list_templatesbutter_explore_templatesbutter_get_templatebutter_list_account_templatesbutter_set_account_templatesWeight caption styles and cover slots, and set the repurposer config — the knobs that shape how goal-based generation fills an account.
butter_set_caption_weightsbutter_set_cover_weightsbutter_set_repurposer_configGoal-vs-achieved posting progress per account and content type — a straight answer without opening the dashboard.
butter_account_posting_progressRun the stdio server yourself to spin up folders, push whole shoots by path or glob — bytes stream straight to storage with no size limit — then assign them to an account.
butter_create_folderbutter_uploadbutter_assign_to_accountAdd Butter to Claude like any custom connector — no clone, no local server. Paste the endpoint, sign in with your Butter account, and you're connected, with a per-user token scoped to just you.
In Claude, open Settings → Connectors → Add custom connector.
Paste https://mcp.hellobutter.io/mcp and add it.
Sign in with your Butter account on the consent screen — connected.
Requires an active Butter subscription. The hosted connector browses your workspace, configures every posting method and drives API posting from the chat; for bulk upload and assignment, use the local CLI below.
Run the stdio server yourself to unlock the heavier tools — bulk upload and assignment on top of
everything the hosted connector does. You'll need Node 18+ and the butter-cli repo.
Upload video and image files by path or glob — bytes stream straight to storage with no size limit — and assign a batch of content ids to an account.
butter_create_folder butter_upload butter_assign_to_accountClone the butter-cli repo and build it. This produces two bins: butter (the CLI) and butter-mcp (the MCP server). You need Node 18+.
npm install && npm run buildAuthenticate and store your token in ~/.butter/config.json. The MCP server and CLI share this login.
butter loginPrefer headless? Set BUTTER_ACCESS_TOKEN in the server env instead. Tokens are short-lived (~15 min) with no refresh — re-run butter login when a call returns 401.
Point Claude Desktop or Claude Code at the built server by absolute path. The config key and server name are both "butter".
{
"mcpServers": {
"butter": {
"command": "node",
"args": ["/ABSOLUTE/PATH/butter-cli/dist/mcp.js"],
"env": { "BUTTER_ACCESS_TOKEN": "..." }
}
}
}env is optional if you already ran butter login. Restart the client, then try "list my Butter clients" to confirm.
The essentials on what the Butter MCP does today, how it posts, and how your data is scoped.