Buffer MCP Server
Manage posts, channels, organizations, and ideas through the Buffer social media API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Buffer MCP Server list my channels"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Buffer MCP Server
An MCP (Model Context Protocol) server for the Buffer social media API. Manage posts, channels, organizations, and ideas through any MCP-compatible LLM client.
Install
pnpm add @damusix/buffer-mcpOr run directly with npx:
npx @damusix/buffer-mcpRelated MCP server: postforme-mcp-pro
Configuration
Variable | Required | Description |
| Yes | Your Buffer API access token. Get one from Buffer Developer Settings. |
The server will exit immediately if BUFFER_ACCESS_TOKEN is not set.
Usage with Claude Desktop
Add to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"buffer": {
"command": "npx",
"args": ["@damusix/buffer-mcp"],
"env": {
"BUFFER_ACCESS_TOKEN": "your-token-here"
}
}
}
}Usage with Claude Code
claude mcp add buffer -e BUFFER_ACCESS_TOKEN=your-token-here -- npx @damusix/buffer-mcpUsage with Other Clients
For Cursor, Windsurf, or any other MCP-compatible client, add @damusix/buffer-mcp as a stdio MCP server with BUFFER_ACCESS_TOKEN set in the environment. Consult your client's documentation for the exact configuration format.
Tools
use_buffer_api
Execute a Buffer API action. Takes an action name and an optional payload object.
Available actions:
Action | Category | Description |
| query | List all organizations on the account |
| query | List channels for an organization |
| query | Get a single channel by ID |
| query | List posts with pagination and filters |
| query | Get a single post by ID |
| query | Get daily posting limits for channels |
| mutation | Create a new post (draft, queued, or scheduled) |
| mutation | Delete a post by ID |
| mutation | Create a new idea in an organization |
Examples:
List organizations:
{
"action": "listOrganizations"
}List posts with pagination:
{
"action": "listPosts",
"payload": {
"organizationId": "abc123",
"first": 10,
"after": "cursor-string"
}
}Create a draft post:
{
"action": "createPost",
"payload": {
"channelId": "abc123",
"text": "Hello world!",
"schedulingType": "automatic",
"mode": "addToQueue",
"saveToDraft": true
}
}buffer_api_help
Get help on available actions. Takes an optional action name or category filter.
List all actions:
{}List only query actions:
{
"category": "query"
}Get detailed help for a specific action:
{
"action": "createPost"
}Development
pnpm install
pnpm test
pnpm run buildLicense
MIT
Available Tools
2 toolsbuffer_api_helpA
Get help on available Buffer API actions — list all actions or get detailed schema info for a specific action
Inputs: action, category.
use_buffer_apiC
Execute a Buffer API action (list organizations, channels, posts, create/delete posts, create ideas, and more)
Inputs: action (required), payload.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
use_buffer_api executes API actions while buffer_api_help provides discovery and schema details. There is no overlap between executing and getting help, so an agent can clearly distinguish when to use each.
Both names contain 'buffer_api', but one uses a 'use_' prefix and the other uses a '_help' suffix. This is a readable but mixed naming convention rather than a consistent verb_noun pattern.
With only two tools, the server feels minimal, but the generic executor plus help tool is a deliberate design that keeps the surface small. It is borderline because one tool does most of the work while the other is purely informational.
The generic executor covers a broad range of Buffer actions, including organizations, channels, posts, and ideas, with additional actions implied by 'and more.' The help tool fills discovery gaps, though the lack of explicit typed tools for individual operations is a minor limitation.
Maintenance
Related MCP Connectors
PostHero MCP server — schedule and publish social media posts from any MCP-compatible AI tool
MCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram.
Hosted MCP server for AI agents to post to LinkedIn profiles and X and upload to YouTube.
Agent-first social media publishing, scheduling, analytics, and unified inbox API + 16-tool MCP server across 18 social platforms (X, LinkedIn, Instagram, YouTube, TikTok, Threads, Bluesky, Reddit, Telegram, Discord, Mastodon, Facebook, Pinterest).
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for Publer social media management API, enabling AI assistants to schedule posts, upload media, pull analytics, and manage accounts across 15+ social networks.1537 npm22MIT
- AlicenseAqualityCmaintenanceMCP server for the Post for Me API, enabling publishing, scheduling, editing, deleting, and analyzing social media posts across 9 platforms from any MCP client.27223 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Buffer social media scheduling via the GraphQL API, enabling post creation, queue management, engagement metrics, and media uploads.2MIT
- AlicenseNot gradedqualityCmaintenanceA full social media management MCP server enabling post, read, schedule, and analyze across Facebook, Instagram, LinkedIn, X/Twitter, Pinterest, and YouTube from any MCP-compatible AI client.MIT