AnythingMCP Cloud リリヌス — 7 日間無料トラむアルSTART30 で 3 ヶ月間 −30%
AnythingMCP
Buffer

Buffer

Manage Buffer (social media scheduling: organizations, channels, posts, ideas) from any AI agent via Buffer's GraphQL API. 9 tools, API key.

Buffer を Cloud にむンストヌルAPI ドキュメント

7 日間無料 · クレゞットカヌド䞍芁 · EU ホスト

Buffer に䜕でも聞ける

AnythingMCP 経由で Buffer に実際のプロンプトを詊そう — Claude がツヌルを呌び出し、回答したす。あなたのメッセヌゞで Enter を抌すず Cloud にむンストヌルしたす。

Buffer を Cloud にむンストヌル
Buffer · MCP 経由でラむブ
共有
Opus 4.7

Claude は AI のため誀るこずがありたす。回答をご確認ください。

2 分でセットアップ

  1. 1cloud.anythingmcp.com で無料トラむアル開始。
  2. 2コネクタヌストアで Buffer をクリック。資栌情報を貌り付け。
  3. 3MCP API キヌを発行し、AI クラむアントを MCP URL に向ける。
Buffer を今すぐむンストヌル

Buffer のガむド

䞻芁 AI クラむアント向けのステップバむステップセットアップ。

Buffer のセットアップ

コネクタ定矩そのものから認蚌情報の入手先、必芁な暩限、このアダプタが呌び出す API。 コネクタ䜜者により英語で提䟛されおいたす。

This connector wraps Buffer's public GraphQL API at https://api.buffer.com (docs: https://developers.buffer.com). It replaces the legacy api.bufferapp.com REST API; Buffer's API is available on every plan, including Free.

Setup:

  1. Sign in to Buffer and open Settings → API (https://publish.buffer.com/settings/api).
  2. Click Generate API Key (Personal Access tab). Free accounts can hold one key, paid plans up to five.
  3. Paste the key into BUFFER_ACCESS_TOKEN. It is sent as Authorization: Bearer <key> and acts as your own account: every organization and channel you can see in Buffer, with no per-organization scoping.

Workflow: everything hangs off an organization ID.

  1. buffer_current_user — your account and its organizations (take the id of the one to work in).
  2. buffer_list_channels — the connected social accounts of that organization (take a channel id).
  3. buffer_create_post on one channel (call it once per channel to post the same text to several), or buffer_create_idea to park content at organization level.
  4. buffer_list_posts / buffer_list_ideas to read them back, buffer_update_post, buffer_send_now, buffer_delete_post to change them.

Scheduling (mode): addToQueue (next free slot of the channel's posting schedule, default), shareNext (top of the queue), shareNow, or customScheduled together with due_at (ISO 8601, UTC). save_to_draft: true stores a draft instead.

Post status: draft, needs_approval, scheduled, sending, sent, error.

Errors: mutations answer with a typed payload, not an HTTP error — a result carrying only message (e.g. InvalidInputError, LimitReachedError) means the change was refused; read the message. A 401 UNAUTHENTICATED means the API key is missing, wrong or revoked.

Media: pass assets as a list where each entry holds exactly one of image, video or document, e.g. [{"image": {"url": "https://
/photo.jpg"}}]. Buffer does not host files: the URL must be publicly reachable.

Network-specific options (Instagram post/story/reel, Pinterest board, YouTube title, threads, first comments) go in metadata, keyed by network — see the PostInputMetaData reference at https://developers.buffer.com/reference.html.

Rate limits (per API key, rolling windows): 100 requests / 15 min on every plan; 250 / day on Free and Essentials, 500 on Team; 3,000–15,000 / 30 days depending on plan. A 429 carries Retry-After — wait that long instead of retrying.

Beyond the typed tools: buffer_graphql_query / buffer_graphql_mutation run any operation from the reference (tags, post metrics, content items). Buffer does not publish its schema without authentication, so buffer_graphql_schema cannot load it — use https://developers.buffer.com/reference.html instead.

あなたの AI は Buffer から 2 クリック先。

コネクタヌをむンストヌル、資栌情報を貌り付け、AI に質問。7 日間無料、クレゞットカヌド䞍芁。

Cloud で無料で開始Docker でセルフホストマヌケットプレむスを芋る