Buffer

No, but your plan sets the request budget. Buffer publishes rate limits per client by plan: Free allows one API key and 3,000 requests over 30 days, Essentials three keys and 7,500, Team five keys and 15,000. All three plans share a 100-request limit per 15 minutes, so the difference is sustained volume rather than burst speed.

It can create and publish posts, and Buffer states that most MCP clients ask you to approve those calls before they run. The write tools are create_post, edit_post, delete_post, create_idea and the generic execute_mutation. Approval is a client behaviour rather than a server guarantee, so check your client prompts before connecting.

Both are documented, for different clients. Claude connects over OAuth with no key to copy, and we confirmed the server issues an OAuth challenge naming auth.buffer.com as its authorization server. For clients without OAuth support, Buffer documents adding the server with an Authorization Bearer header carrying a personal API key instead.

Up to a day behind. Buffer documents that metrics refresh once a day, so values can lag the social network by that much. Post count, reactions and comments always come back, while reach, impressions and engagement rate appear only when every channel in your filter supports them. A metrics query can span at most 365 days.

Probably because the edit dropped a field the post needs. Buffer validates every edit as a whole post rather than merging it into the stored version, so an assistant has to read the post with get_post first and carry the current assets and metadata forward. Changing only what you asked for means preserving everything you did not.

Anthropic's directory lists 15. Buffer's own MCP guide documents 20, the extra five being post-template tools for listing, reading, creating, updating and deleting templates. Buffer's count is the larger and more recent, so treat 15 as what Anthropic recorded rather than the server's full surface.