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.
11 tools
How to connect
How to connect Buffer to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Buffer once
-
Open Connections, choose Add connection, and pick Buffer.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Buffer MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Buffer MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Buffer MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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”
Compare
Elaichi vs Zapier MCP vs Composio for Buffer
All three can connect Buffer to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Buffer tools | Allow or restrict single Buffer tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Buffer call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
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
ElaichiToolsToolboxes
Every team gets its own Buffer toolbox.
Social, content and support each see a curated set of Buffer tools.
- Social
- Content
- Brand
- Campaigns
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 logLaunching 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 Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch posts
Buffer
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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 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.
Does the Buffer MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Buffer is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Buffer?
Yes. Both let Claude, ChatGPT or Cursor use Buffer. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Buffer call.
How is Elaichi different from Composio for Buffer?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Buffer: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Buffer in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.