Connect Buffer to Claude Code

Let Claude draft and schedule posts straight into your Buffer queue. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Buffer to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Buffer, you add a Buffer MCP server: a small hosted service that exposes Buffer's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Buffer account. No API keys pasted into config files.

claude mcp add --transport http buffer https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Buffer once connected?

Full read-write Buffer access lets Claude draft a post, attach it to the right channel, set a scheduled time or drop it in the queue, edit or reschedule pending posts, and update drafts before they publish. The composing and scheduling that used to mean copy-paste into Buffer happen where the calendar already lives.

Draft a post and add it to a specific channel's queue
Schedule a post for a chosen date and time
Edit the copy or media on a pending scheduled post
Reschedule a post to a new date and time in the queue
Move a draft into the publishing queue after you approve it
Pull recent post analytics and propose follow-up content

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Buffer access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Buffer API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Buffer changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Buffer connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Buffer connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Buffer account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Buffer's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Buffer?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Buffer account it signs in with. Revoking access is one click in Buffer.

More on the Buffer connector

Buffer connector for claude.ai Braze + Claude Code Iterable + Claude Code Customer.io + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us