Skip to content

Marketing Automation

Buffer MCP connector

The Buffer connector lets Claude, ChatGPT, Cursor, and other MCP clients read, draft, reschedule, and delete Buffer posts, save ideas, and check channels and daily posting limits, with each person signed in as themselves and every action logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Buffer to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Buffer once

  1. Open Connections, choose Add connection, and pick Buffer.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Buffer API key. One person generates a token in Buffer and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

buffer
Buffer
Beamer
ClickSend
Dotdigital
Dub
Extole
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Buffer to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Buffer to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Buffer to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Buffer to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Buffer through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Social media

    Fill next week's queue from one brief

    Hand the agent a campaign brief and have it draft posts for each connected Buffer channel, ready for you to review before anything is scheduled.

  • Marketing

    Check what is scheduled before a launch

    Ask what is queued across your Buffer channels for launch week, then update the copy or timing of any post that no longer fits the plan.

  • Content

    Park ideas while they are fresh

    Drop half-formed angles from a meeting straight into Buffer as ideas so the team can shape them into posts later.

  • Communications

    Pull a post before it goes out

    When news breaks or a message is no longer appropriate, find the scheduled Buffer post and delete it in one request instead of hunting through the queue.

  • Agency

    Confirm which channels each client has

    List the Buffer organizations and channels you manage so you know exactly where a client's posts will land before you draft them.

  • Marketing operations

    Spot channels close to their daily limit

    Check Buffer's daily posting limits per channel and shift posts to another day before a queue is refused.

Try asking

  • “List every Buffer post scheduled this week by channel”
  • “Draft a Buffer idea for Thursday's product launch”
  • “Which Buffer channels are near their daily posting limits”

See all 11 Buffer tools below

AI tools

Buffer tools for your AI agents

11 tools are ready to call through Elaichi's MCP endpoint the moment you connect Buffer, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Buffer gets you

6 screens from the product, each doing one job for your Buffer account.

The agent

Ask about Buffer posts in plain language.

Answers come from live Buffer posts, channels and ideas, not a stale export.

  • posts
  • ideas
  • channels
  • organizations

Ask Elaichi to work across your apps.

List every Buffer post scheduled this week by channel

Draft a Buffer idea for Thursday's product launch

Which Buffer channels are near their daily posting limits

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Buffer.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

11 Buffer tools ready without custom code.

Posts, ideas, channels, organizations and daily posting limits, each with its own methods.

  • List all Buffer posts
  • Create a Buffer post
  • Get single Buffer post by ID
  • Update a Buffer post by ID
ElaichiTools
Tool Action Description
List all Buffer posts List List Buffer posts for an organization using cursor-based pagination. Returns: id, text, status, dueAt, channelId, channelService, createdAt, updatedAt, schedulingType. Required: organizationId.
Create a Buffer post Create Create a new Buffer post on a single channel. Returns: id, text, status, dueAt, channelId, channelService, schedulingType. Required: channelId, text, schedulingType, mode. Provide dueAt only when mode is customScheduled. One API call creates one post on one channel.
Get single Buffer post by ID Get Get a single Buffer post by id. Returns: id, text, status, dueAt, sentAt, channelId, channelService, createdAt, updatedAt, schedulingType, isCustomScheduled. Required: id (path).
Update a Buffer post by ID Update Update the text or scheduled time of an existing Buffer post by id. Returns: id, text, status, dueAt, channelId. Required: id (path).
Delete a Buffer post by ID Delete Delete a Buffer post by id. Returns the id of the deleted post on success. Required: id (path).

Toolboxes

Every team gets its own Buffer toolbox.

Social, content and support each see a curated set of Buffer tools.

  • Social
  • Content
  • Brand
  • Campaigns
ElaichiToolboxes
Name Source template Tools Created

Social toolbox

Buffer · posts and channels

Buffer starter 18 Mar 4, 2026

Content toolbox

Buffer · ideas and drafts

9 Mar 2, 2026

Brand toolbox

Buffer · organizations and channels

24 Feb 27, 2026

Campaigns toolbox

Buffer · scheduled posts

Buffer starter 6 Feb 19, 2026

Support toolbox

Buffer · reply posts

31 Jan 30, 2026

Analytics toolbox

Buffer · posting limits and volume

12 Jan 22, 2026

Shared connections

Teammates publish without touching Buffer credentials.

See who connected each Buffer account and how many teams and members use it.

  • Social EMEA
  • Brand Global
  • Content Studio
  • Campaigns AMER
ElaichiConnections
Connection Scope Status Access
BU

Buffer (Social EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
BU

Buffer (Brand Global)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
BU

Buffer (Content Studio)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
BU

Buffer (Campaigns AMER)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
BU

Buffer (Support Social)

Connected by Clara Nowak

Personal • Active Not shared
BU

Buffer (Founder Channels)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Buffer post change has a name on it.

When, who, what happened, type and resource for each call into Buffer.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Buffer Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Buffer Posts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Buffer Posts List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your Buffer digest.

Six steps fetch posts, group them, draft a digest, wait for approval, then post.

Buffer digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch posts

    Buffer

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Buffer

    Queued

Collections and dashboards

Buffer numbers arrive before anyone asks.

Four metrics, 14 days of posts created and a team breakdown, refreshed on schedule.

Buffer health

Refreshed 4 minutes ago · every 15 minutes · from the posts collection

Live

Posts

1,284 ↓ 12%

Ideas

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Posts created

Last 14 days

By team

Share of activity

Social EMEA 34%

Brand Global 27%

Content Studio 21%

Campaigns AMER 18%

FAQ

Frequently asked questions

How do I connect Buffer to Claude?

In Elaichi, choose Buffer and paste your Buffer API key when asked; that is the whole sign-in step, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and Buffer is ready to use.

Does Buffer work with ChatGPT and Cursor as well as Claude?

Yes. Once Buffer is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Buffer once and every client picks it up.

What can an AI agent actually do with my Buffer data?

With Buffer connected, an agent can list the posts in your queue, open a specific post, draft new posts for any channel, change the copy or timing of a scheduled post, and delete one that should not go out. It can also save ideas, show which Buffer organizations and channels you have access to, and check each channel's daily posting limit.

Does connecting Buffer give the AI access to every organization and channel?

No. When you connect Buffer, the agent can only see the organizations and channels your own Buffer account can see, because every request runs inside your access. Elaichi can narrow that further, for example to read-only or to specific actions, but it can never grant more than your Buffer account already has.

Can my team share one Buffer connection?

Yes. One person connects Buffer in Elaichi and shares it with a team, and nobody else ever handles the Buffer API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who scheduled or deleted a Buffer post.

Can I stop an agent from deleting or changing posts in Buffer?

Yes. In Elaichi you can restrict the Buffer connection per action, so an agent may be allowed to read and draft posts but not update or delete them. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt, however worded, can reach it.

What happens to a Buffer connection when someone leaves?

When you offboard a person in Elaichi, their access to Buffer through every client ends at once. A Buffer connection that was shared with a team keeps working for everyone else. If you want to remove Buffer entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Buffer in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.