Model Context Protocol

Your posting pipeline, in one conversation.

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.

Connect Butter

API, My Phones, Cloud Phones or manual Scoped to your account Hosted or local

Claude

higgsfield butter

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.

Chaining 12 Butter tools across both connectors

butter_create_folderbutter_uploadbutter_assign_to_accountbutter_explore_templatesbutter_set_account_templatesbutter_set_repurposer_configbutter_update_account_settingsbutter_set_caption_weightsbutter_set_cover_weightsbutter_set_api_posting_schedulebutter_set_timezonebutter_account_posting_progress

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.

Connect Butter with

Codex ChatGPT Claude VS Code Cursor n8n

One hosted Streamable HTTP endpoint with Butter OAuth. ChatGPT access uses a workspace-approved custom app.

Posting methods

Not just the API. Post four ways — per post type.

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.

One account, three routes

Reels

API posting

Stories

My Phones

Carousels

Manual

Set in one call

butter_update_account_settings reel_post_method · story_post_method · carousel_post_method

API posting

api

Publish 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 Phones

my_phones

Post from your own physical phones.

Control your own devices — content goes out from real handsets you’ve connected and manage yourself.

Cloud Phones

geelark

Post via managed cloud phones.

Fully cloud-hosted devices post on your behalf — no hardware for you to run.

Manual

manual

You 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.

Repurposing

Content from anywhere → on-brand viral variants.

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.

Raw content in, variants out

Content from anywhere Clips you upload, renders from Higgsfield, anything you drop in.

Butter’s generation engine Trending audio, AI overlays, captions and covers applied automatically.

On-brand viral variants A steady stream of fresh cuts, any vibe — queued and ready to post.

Two ways to generate

Parametric Templates

Parametric

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_settings

repurposer_enabled · parametric_repurpose_enabled

Templates

Styled 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_weights

Trending 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.

Recipes

One sentence in. The whole workflow out.

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:

Route Hosted connector

You

"Post @youraccount’s reels via API, its stories from My Phones, and carousels manually."

Tools chained

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.

What it does

Your Butter workflows, scoped to you

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. Approved workspaces can separately request local bulk upload.

Browse

Find clients & accounts

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_account

Configure

Change any account setting

Posting 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_schedule

Route

Pick a posting method per type

Route reels, stories and carousels each to API posting, My Phones, Cloud Phones or manual — independently, in a single settings call.

butter_update_account_settings

Publish

Connect & post via API

Get 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_now

Templates

Discover & assign templates

Browse 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_templates

Tune

Steer the generation mix

Weight 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_config

Report

Check progress against goals

Goal-vs-achieved posting progress per account and content type — a straight answer without opening the dashboard.

butter_account_posting_progress

Local files

Private bulk-upload CLI

Approved workspaces can request the separately distributed local CLI to push shoots by path or glob. It is not required to connect the hosted MCP.

butter_create_folderbutter_uploadbutter_assign_to_account

Available now

One-click hosted connector

Add Butter to Codex, ChatGPT, Claude, VS Code, Cursor, or n8n — no clone, local server, API key, or copied token. Paste the endpoint, approve Butter’s OAuth consent screen, and the connection stays scoped to your user.

In Claude, open Settings → Connectors → Add custom connector.

Paste https://mcp.hellobutter.io/mcp and add it.

Requires an active Butter subscription or approved rollout access. The hosted connector browses your workspace, configures every posting method and drives API posting. Codex, Claude Code, VS Code, Cursor, and n8n connect to this same endpoint with the setup below.

Codex · OAuth MCP

Connect Butter to Codex

Add the hosted endpoint once, authorize your Butter account, and use the same connection from the Codex app, CLI, or IDE extension on that host.

Install or update Codex CLI

Install the current Codex CLI release so remote OAuth MCP commands are available.

npm install --global @openai/codex

If your installed release supports self-update, codex update is also available.

Add Butter to Codex

Run the official Codex CLI command for a remote Streamable HTTP MCP server.

codex mcp add butter --url https://mcp.hellobutter.io/mcp

The Codex app, CLI, and IDE extension share this MCP configuration on the same Codex host.

Sign in with Butter

Start the OAuth flow and approve access in the browser window Codex opens.

codex mcp login butter

Codex uses S256 PKCE and a local loopback callback. No API key or copied access token is needed.

Verify the connection

Confirm Butter is enabled, then begin with a read-only workspace request.

codex mcp list

Then ask: List my Butter clients.

If an old attempt is cached, run codex mcp logout butter and repeat the login command.

VS Code · Cursor · more

Use the same endpoint everywhere

Butter supports remote Streamable HTTP, OAuth discovery, dynamic client registration, and S256 PKCE. Start with the native setup for your client.

ChatGPT

Workspace settings → Apps → Create

Name: Butter
URL: https://mcp.hellobutter.io/mcp

Enable developer mode, create the app, scan its tools, and complete Butter OAuth. Workspace admins control publishing and access.

Claude.ai / Desktop

Settings → Connectors → Add custom connector

Name: Butter
URL: https://mcp.hellobutter.io/mcp

Add the connector and approve Butter in the browser. No repository, API key, or local server is required.

VS Code

Command Palette → MCP: Open User Configuration

{
  "servers": {
    "butter": {
      "type": "http",
      "url": "https://mcp.hellobutter.io/mcp"
    }
  }
}

Add this to mcp.json, start Butter from MCP: List Servers, and complete the browser sign-in.

Cursor

Cursor Settings → MCP → Add custom MCP

{
  "mcpServers": {
    "butter": {
      "url": "https://mcp.hellobutter.io/mcp"
    }
  }
}

Add it in Cursor Settings → MCP. Cursor discovers OAuth from the Butter endpoint.

Another MCP client? Use Streamable HTTP at https://mcp.hellobutter.io/mcp with OAuth 2.1 and S256 PKCE. Local clients may use an IP-literal loopback callback; hosted clients need their exact HTTPS callback approved by Butter.

Claude Code · works today

Connect from Claude Code

Claude Code connects directly to Butter's hosted OAuth MCP. You do not need a Butter repository, local server, API key, or copied access token.

Hosted MCP, from Claude Code

No repo needed

One terminal command registers Butter. Claude Code then opens Butter's OAuth consent flow and keeps the connection authenticated.

Update Claude Code

Use the current Claude Code release before adding a remote OAuth MCP server.

claude update

Already current? Continue to the next step. New users should install Claude Code from Anthropic’s official setup guide.

Add Butter

Run this in your terminal. Claude Code connects directly to Butter’s hosted MCP over HTTPS.

claude mcp add --transport http butter https://mcp.hellobutter.io/mcp

No Butter repository, local server, API key, or access token is required.

Authorize Butter

Start Claude Code, open its MCP menu, select Butter, and complete the Butter consent screen in your browser.

claude
/mcp

Claude Code stores and refreshes the OAuth connection. If the browser does not open, copy the authorization URL shown in the terminal.

Verify read-only access

Ask for a safe workspace read before requesting any publishing or configuration changes.

List my Butter clients.

A client list confirms the hosted MCP connection and your Butter authorization are working.

n8n · OAuth connection

Use Butter in scheduled n8n workflows

Connect the standalone MCP Client node for explicit tool calls, or MCP Client Tool when an AI Agent should choose the Butter action. Both use the hosted endpoint and Butter’s OAuth consent.

Remote HTTP MCP with OAuth

No repository needed

n8n registers its own OAuth client, opens Butter’s approval screen, and refreshes the connection for unattended executions.

Add an MCP Client

Use the standalone MCP Client node for deterministic workflows, or attach MCP Client Tool to an AI Agent.

Transport: HTTP Streamable
Endpoint: https://mcp.hellobutter.io/mcp

Use a current n8n release that includes MCP OAuth2 authentication.

Create the OAuth credential

Set Authentication to MCP OAuth2, create a new credential, and leave dynamic client registration enabled.

Authentication: MCP OAuth2
Dynamic Client Registration: On

Do not use Bearer Auth, Header Auth, a Butter API key, or the Butter source repository.

Approve and verify

Complete Butter’s consent screen, then choose a read-only Butter tool before enabling scheduled executions.

Tool: butter_whoami
Then: butter_list_clients

Self-hosted n8n: Butter must approve the exact HTTPS OAuth callback shown by your instance, including any /n8n subpath.

Install guides

Choose your platform.

Every supported client connects to the same hosted Butter endpoint. Pick your platform for the exact setup path.

Codex

Install the CLI, add Butter, then complete OAuth in your browser.

Install or update Codex CLI

Install the current Codex CLI release so remote OAuth MCP commands are available.

npm install --global @openai/codex

If your installed release supports self-update, codex update is also available.

Add Butter to Codex

Run the official Codex CLI command for a remote Streamable HTTP MCP server.

codex mcp add butter --url https://mcp.hellobutter.io/mcp

The Codex app, CLI, and IDE extension share this MCP configuration on the same Codex host.

Sign in with Butter

Start the OAuth flow and approve access in the browser window Codex opens.

codex mcp login butter

Codex uses S256 PKCE and a local loopback callback. No API key or copied access token is needed.

Verify the connection

Confirm Butter is enabled, then begin with a read-only workspace request.

codex mcp list

Then ask: List my Butter clients.

If an old attempt is cached, run codex mcp logout butter and repeat the login command.

Questions

Good to know.

The essentials on what the Butter MCP does today, how it posts, and how your data is scoped.

Get started

Put your library on autopilot.

Connect the Butter MCP and let your agent handle settings, posting methods, publishing, templates and uploads — in plain language, scoped to your accounts.

Choose your platform