Buffer MCP server for Claude, Codex and Cursor

What your AI apps can do with Buffer

Create and schedule posts
Review channels and queues

Buffer MCP tools

17 tools, taken from the publisher's documentation on 31 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`get_account`	Returns the signed-in user and their organizations with IDs, plan limits and member counts.
`list_channels`	Lists an organization's connected social channels with ID, name, service, type and connection status.
`get_channel`	Returns details for one channel, such as posting schedule, queue status, timezone and service-specific data.
`list_posts`	Lists an organization's posts, filterable by channel, status, tag and date, with optional metrics.
`get_post`	Reads one post in full, including metadata, assets, allowed actions, errors and optional analytics.
`create_post`	Schedules or publishes a post on one channel, with service-specific metadata, threads and assets.
`edit_post`	Modifies an existing post; omitted fields are kept, sent arrays or metadata objects replace the stored ones.
`delete_post`	Permanently deletes a post when deletion is among its allowed actions.
`get_aggregated_post_metrics`	Returns totals and averages of post analytics over a date range of up to 365 days.
`list_ideas`	Lists an organization's ideas, filterable by tag.
`list_idea_groups`	Lists the ideas board columns with ID, name and lock status.
`create_idea`	Saves a new idea without scheduling or publishing anything.
`list_post_templates`	Lists the public, internal and private post templates, optionally filtered by visibility.
`get_post_template`	Reads one template's body, title, description, emoji, visibility and timestamps.
`create_post_template`	Creates a private or internal post template that may contain placeholders.
`update_post_template`	Updates only the template fields that are sent.
`delete_post_template`	Permanently deletes a post template.

Suggested access for each AI app

The documentation this list comes from doesn't mark Buffer's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Buffer connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Buffer to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Buffer tool, give Cursor only the read tools, or keep Buffer away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Buffer MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Buffer in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Buffer endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http buffer 'https://mcp.buffer.com/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "buffer": {
      "url": "https://mcp.buffer.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Buffer MCP documentation for what your client needs.

Before you connect

A Buffer account. Sign-in uses your Buffer permissions.

Server details

Detail	Value
Publisher	Buffer
Endpoint	`https://mcp.buffer.com/mcp`
Authentication	Browser sign-in
Categories	Marketing & research, Communication
Tool list	17 tools, observed 31 October 2026 (docs)

Buffer MCP documentation