# 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. Source: https://elaichi.ai/connectors/buffer/ ## Facts | | | | --- | --- | | Application | Buffer | | Category | Marketing Automation | | AI tools | 11 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Buffer is connected - 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 ## Connect Buffer in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Buffer. 2. Optionally set Share with, 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Buffer tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Buffer to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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. ## Connect Buffer to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Buffer to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Buffer tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Buffer through Elaichi ### Fill next week's queue from one brief Social media. 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. ### Check what is scheduled before a launch Marketing. 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. ### Park ideas while they are fresh Content. Drop half-formed angles from a meeting straight into Buffer as ideas so the team can shape them into posts later. ### Pull a post before it goes out Communications. 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. ### Confirm which channels each client has Agency. List the Buffer organizations and channels you manage so you know exactly where a client's posts will land before you draft them. ### Spot channels close to their daily limit Marketing operations. Check Buffer's daily posting limits per channel and shift posts to another day before a queue is refused. ## 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. ## All 11 Buffer tools Every tool below is callable through https://api.elaichi.ai/mcp once Buffer is connected, subject to the toolbox it is in and the restrictions on the caller. - **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). - **Create a Buffer idea** (Create). Create a new idea in Buffer for a given organization. Returns the created idea including its id, organizationId, position, createdAt, and content (title, text). Required: organizationId. - **List all Buffer account** (List). Get the authenticated Buffer account details. Returns: id, email, backupEmail, avatar, name, timezone, and createdAt. - **List all Buffer organizations** (List). List all organizations associated with the authenticated Buffer account. Returns: id, name, channelCount, ownerEmail, limits (channels, members, scheduledPosts, ideas), and total member count. - **List all Buffer channels** (List). List all Buffer channels for an organization. Returns: id, name, service, displayName, timezone, isDisconnected, isLocked, and isQueuePaused for each channel. Required: organizationId. - **Get single Buffer channel by ID** (Get). Get a single Buffer channel by id. Returns the full channel object including id, name, service, displayName, avatar, timezone, isDisconnected, isLocked, isQueuePaused, scopes, and createdAt. - **List all Buffer daily posting limits** (List). Check daily posting limit status for one or more Buffer channels on a date. Returns per channel: channelId, sent, scheduled, limit, isAtLimit. Required: channelIds (array of channel IDs, same organization). Optional: date (ISO 8601 UTC; defaults to today).