Buffer MCP Server: What It Does, What It Costs and How to Connect It

The Buffer MCP server is a remote server, run by Buffer at the address mcp.buffer.com/mcp, that lets an AI assistant work inside your Buffer account. Once it is connected you can ask Claude or ChatGPT, in ordinary sentences, what is in your queue this week, to turn a few notes into a LinkedIn post and put it on Thursday, or to move a post to another day. Buffer's MCP page describes the result as drafting, scheduling and checking your upcoming posts from the tool you already have open, without switching tabs.

Buffer announced the server in a changelog entry titled Talk to Your Agent via MCP in June 2026. At launch it named Claude, ChatGPT and Perplexity. The list has grown since: Buffer's help article on connecting AI assistants now gives setup steps for Claude, ChatGPT, Cursor, Zapier, n8n, Notion, Perplexity, Manus, Antigravity, Grok and Raycast, and says Claude Code, Codex and any other client that speaks the protocol can connect as well.

MCP is short for Model Context Protocol. The official MCP introduction describes it as an open standard for linking AI applications to outside systems, so one server works in many assistants instead of needing a plugin for each. For a social media tool, that means the assistant does the talking and the tool does the publishing. Buffer's server is a door into Buffer: it can do the things you would otherwise open Buffer to do, using the channels, queue and posting schedule you set up there.

It moves words into a queue and reads the queue back well. It adds no design studio and no source of news, which the sections below come back to. For Buffer the scheduler, see our Buffer comparison for app founders.

Two of Buffer's pages describe what happens to a post your assistant creates, and they read slightly differently. Buffer's MCP page says posts land in your Buffer queue as drafts or scheduled posts, so you can look at everything before it goes live. Buffer's developer guide is more precise: the create tool can publish immediately, the delete tool cannot be undone, and you should leave your client's approval prompts switched on because that prompt is the last chance to catch a misread request.

Both are true once you know the defaults. If the assistant does not ask for a draft, a new post joins the queue and Buffer publishes it at the next open slot in your posting schedule, without another click from you. If the assistant chooses the share now mode, the post goes out at once. A draft only happens when the assistant sets the save as draft option, which it will do if you ask for one. So the safe habit is to say draft in the request, for example: save this as a Buffer draft, do not schedule it.

Approvals are a separate matter. Buffer's post statuses include needs approval, and the list tool can filter by it, so an assistant can show you what is waiting. Approval workflows themselves are a Team plan feature, per Buffer's pricing, and the MCP tool list has no tool named for approving a post. Moving a draft into the queue is an edit, made with the same tools as any other change, under the same approval prompt in your client.

Reminders are the third path. Every create call says whether Buffer should publish automatically or send you a notification to post by hand. Reminders are how Buffer handles account types it cannot publish to directly, such as Instagram personal profiles and Facebook groups, so an assistant can still put those posts on your calendar.

Buffer's MCP guide says calls through the server count against the same limits as any other use of the API, per client, across a rolling 15 minute, 24 hour and 30 day window. They are counted per request, not per conversation. Asking the assistant to list your channels, read the week's posts and then edit one of them spends several requests from the same budget. Buffer's help article adds that personal keys and connected assistants share one usage meter.

Here is a worked example with round numbers. Alex plans a week of posts on the Free plan with three channels. The assistant reads the account (1 request), lists the channels (1), lists the posts already queued (1), then creates five posts on each of the three channels (15). That is 18 requests, well inside the 100 allowed in 15 minutes and the 250 allowed in a day. The 3,000 a month on Free averages about 100 a day: plenty for one person, tight for an agency.

The bigger limit on Free is not requests. It is the 10 posts that can wait in each channel's queue at one time. An assistant that tries to schedule a month of daily posts on one Free channel will stop at ten. Each time a post publishes, a slot opens again.

Every successful response carries the quota left in each window, so a well behaved assistant can pace itself instead of hitting the wall.

Buffer is direct about what a connection reaches, and it is worth reading before you connect. Buffer's MCP guide says a connection acts with the same reach over your content that you have. Buffer's authentication guide adds that a key reaches every organization and channel in your account, with no way to open one workspace to an assistant while keeping another closed. If you run a personal brand and a client in the same login, the assistant can see and change both.

Keys are more flexible than they were. Buffer's guide to creating an API key lets you choose what each key may do: read posts, write posts, read and write ideas, read and update account details, and read post analytics. All of them are ticked by default. You can untick everything except reading posts to make a key that can look but never publish, and you pick an expiry of 7, 30, 60 or 90 days or a year. API access needs a verified email address.

Treat a key like a password. Clients often keep it in a plain text settings file, so keep it out of anything you share or commit, and give each tool its own key so removing one breaks nothing else.

Buffer also warns about lookalikes. Its guide says the only official address is mcp.buffer.com/mcp, and that a one click install found on a third party list deserves a careful read before you trust it with your account. If a connector asks for your key on a site that is not Buffer's, stop there.

When a post your assistant created sits in Buffer and never reaches Instagram, it was often never set to go out on its own. Buffer's article on automatic Instagram posting says automatic publishing works only for professional accounts, meaning Business or Creator, and only for posts that meet Instagram's rules. Anything else is scheduled as a notification: Buffer sends it to the Buffer app on your phone and you finish posting it in Instagram yourself. If no phone is linked to your Buffer account, that notification has nowhere to go and the post fails.

Buffer lists what quietly turns a post into a notification: the Enable Notifications by default setting in the Instagram channel, an image outside a ratio of 4:5 to 1.91:1, a video outside 4:5 to 16:9, a Reel shorter than 3 seconds or longer than 15 minutes, and features such as music, product tags, or links and text on Stories. Even a ratio of 0.799 against a minimum of 0.8 is enough. Since the create tool takes a choice between automatic publishing and a reminder, ask for automatic in your request, then look for the Notify label on the post in your queue.

When the post did try and failed, Buffer's Instagram error library explains the message. The common ones are lost authorization, fixed by reconnecting Instagram through Facebook with every permission ticked and refreshing the channel; an account switched back to personal; Instagram's cap of 25 posts in 24 hours; images over 8 MB; and Instagram's spam filter, which Buffer suggests getting past by rewording the caption, using fewer hashtags and removing links. Your assistant can read the failure message with the get_post tool, so you can ask it why a post errored without opening Buffer.

TikTok has the same two paths. Buffer's TikTok guide describes automatic publishing and Notify Me, and says Buffer falls back to Notify Me for content TikTok will not take automatically, such as a video over the length limit. The guide also lists 5 hashtags per post and 25 posts per 24 hours, and says TikTok scheduling is only on Buffer's current plans, not legacy ones. Check those first when Buffer is not posting to TikTok.

Inside Buffer, Canva is a built in integration. Buffer's Canva guide has you open the composer, pick your channels, choose Canva from the integrations menu, sign in, make or pick a design and click Return to Buffer. A design made for several networks at once comes out square at 1080 by 1080. The same guide lists the limits: web only, not in Buffer's mobile apps, PNG files only, one image at a time, no resizing and no access to your Canva Brand Kit. For an animated design, export an MP4 from Canva and upload it to Buffer by hand.

With an assistant, you connect both servers in one chat: Canva's connector makes and exports the design, and Buffer's server puts it in the queue. There is one trap. Buffer's API takes no file uploads. Buffer's media hosting guide says you pass a public link, that Buffer fetches the file when the post goes out, which for a queued post can be days later, and that signed links which expire often work when the post is created and then fail on the day. Canva's export links are that kind of link: Canva's export tool page says they expire and should not be stored.

So for anything that is not going out right away, put the Canva export somewhere stable first, such as your own site or a storage bucket with public links, and give Buffer that address. Or use a publisher that keeps its own copy: Spreadcast's upload tool copies a Canva export into its own storage the moment you add it, and our Canva MCP server guide shows that handoff step by step.

It does not design the post picture. No tool in Buffer's MCP guide makes an image, a carousel or a video. The create tool attaches media you already have, by link, and Instagram and TikTok refuse a post without it. So the picture comes from you, from a design tool such as Canva, or from whatever your assistant can make on its own. Buffer's AI Assistant inside the Buffer composer is a writing tool: it suggests ideas, rewrites, shortens and adapts text for each network, and the product page describes no image design.

It does not know what is happening in your business. The server reads what is already in Buffer: channels, posts, ideas and templates. It has no feed of your product news, your releases or your reviews. Every post starts from what you type into the chat, or from what your assistant can find elsewhere.

It has no tools for comments or messages. Buffer's app has a community inbox for replies, but the MCP tool list does not include it, so an assistant cannot read or answer comments through the server.

It does not check a post before saving it. The create tool validates on save, with no separate dry run.

It has no tool named for approving a draft, and its numbers are daily: post metrics refresh once a day, and reach and impressions show only when every channel in the request supports them.

Search GitHub for a Buffer MCP server and you will find community projects next to Buffer's own. Buffer's official server is hosted by Buffer, so there is nothing to install or clone: you add the address and sign in. If a project's code calls api.bufferapp.com, it is built on the legacy REST API, which Buffer's migration guide helps developers move away from, toward the GraphQL API at api.buffer.com.

For terminal work, Buffer has its own tool. Buffer's CLI guide describes a command line app installed from npm that needs Node.js 18 or later, reads your personal key and returns JSON from every command. It ships skill files for Claude Code and Codex, and one command installs the skill, so Claude Code can schedule Buffer posts through the CLI without the MCP server. Both count against the same request limits on your plan.

The official code Buffer keeps on GitHub is its sample apps repository, meant for developers who build apps that other people connect to Buffer. A server that asks for your Buffer password, rather than a key or a Buffer sign in, is not Buffer's.

The two get confused because both involve AI, but they sit on opposite sides. The Buffer AI Assistant is built into Buffer. You open the composer, type a prompt and it drafts or reworks the text of a post: ideas, a rewrite, a shorter or longer version, a different tone, a version for another network. Buffer's pricing page lists it on every plan with unlimited use.

The MCP server is the reverse direction. Your own assistant, Claude or ChatGPT, does the thinking in its own window and uses the server to reach into Buffer. You use the model you already pay for, and Buffer is where the result lands.

Neither one makes the image. If writing is your bottleneck, either will help. If the bottleneck is the picture, or knowing what to post about in the first place, you need something else in the chain. Buffer's own post on posting from Claude, written by a Buffer content creator, shows the typical setup: the ideas, screenshots and Canva files are gathered by hand, and Claude shapes them and sends them to the queue.

Spreadcast is a social media tool for people who make apps on the App Store, and it runs its own MCP server at spreadcast.app/api/mcp. Where Buffer's server moves posts you wrote into a queue, Spreadcast's server makes the post. The assistant reads your app's brand kit and designs the picture in your colors, fonts and logo, with a real screenshot of your app in an iPhone frame. It can design a carousel of 3 to 8 slides at 1080 by 1350. It writes a caption for each network, checks the post against each network's rules and saves it as a draft.

It also knows what is worth posting. Spreadcast watches your App Store listing and finds moments: a new version with what changed, taken from your release notes, or a rating milestone worth a thank you. The assistant starts from those, so you are not inventing topics in the chat.

Drafts are the default by design. When you connect Claude or ChatGPT you sign in with Spreadcast, and the consent screen asks one question with two answers: Make Drafts or Make and Publish. Make Drafts is picked for you. With it, the assistant can design, write and save but cannot schedule or publish, however the request is worded. Approving a draft is its own step.

Spreadcast publishes to Instagram, TikTok, LinkedIn, Facebook, Threads, Pinterest, Bluesky, Telegram and Discord, and YouTube and Mastodon connect too. The Free plan includes the MCP server and saves drafts. Pro, at $29 a month for one app, adds scheduling and publishing to every network you connect, with the design and the captions included in that price. Studio, at $79 a month, covers 5 apps, each with its own brand, and 3 seats. The full tool list and setup are on our social media MCP server page, and the MCP overview gives the short version.

Buffer and Spreadcast are two of about ten tools with a social media MCP server today. Metricool, Postiz and Hootsuite are among the others. Our roundup of the best social media MCP servers puts all of them side by side, with free plans, sign in methods and what each can and cannot do.

For Buffer itself, see the Buffer alternatives roundup, the Buffer vs Hootsuite comparison and the guide to scheduling social media posts with ChatGPT.