Skip to main content
Glama
Buffer MCP Server

Buffer MCP Server

by thenavidm

Related Servers

Alternatives to Buffer MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to upload and schedule videos, images, carousels, and text posts across 17 social platforms, read analytics, and reply to comments through a hosted OAuth connection.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables publishing and scheduling posts to Facebook, Instagram, YouTube and other channels through Buffer, with Cloudinary media upload and validation plus analytics tools. It provides 23 tools covering channel and post management, media probing and upload, and performance insights for AI-driven content operations.
      23
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants and autonomous agents to connect to social media accounts and manage, generate, schedule, upload media for, and publish content across Facebook Pages, YouTube, TikTok, Instagram, and X, plus maintain a content pipeline.
      14
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to write, schedule, publish, and measure social media posts across LinkedIn, Bluesky, Mastodon, and YouTube, plus manage media and queue slots, through one OAuth URL with no install or API key. It also covers retrying, cancelling, restoring posts and reading analytics, with reversibility safeguards around irreversible publishing.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Social media scheduling and publishing for AI agents. 17 validation-first tools to post to X, LinkedIn, Instagram, TikTok, YouTube, Reddit, Discord, Telegram, and more through one connected workspace.
      164 npm
      110
      MIT

    TDQS

    B3.2/5.0

    Scored across 41 tools

    Disambiguation3/5

    Most resource-specific tools (content items, posts, templates, ideas, audio) are reasonably distinct, though pairs like create_content_item vs create_content_item_draft and update_content_item vs update_content_item_draft require careful reading. The generic escape-hatch tools (graphql_query, graphql_mutation, query_pages, preview_operation, get_operation_schema) heavily overlap with every named tool and with each other, creating real misselection risk.

    Naming Consistency4/5

    The surface is overwhelmingly predictable verb_noun snake_case (create_/get_/update_/delete_/list_ + resource), which makes scanning easy. Minor deviations exist: edit_post instead of update_post, the versioned get_tags_v2, and list_accounts vs get_account blur the verb convention slightly.

    Tool Count2/5

    41 tools is well above the comfortable band for an agent surface, and several are near-duplicates or meta-tools (five GraphQL/validation helpers). While the domain is genuinely broad, the count is heavy enough to dilute selection accuracy and inflate context.

    Completeness4/5

    Coverage is strong: full CRUD for content items, posts, and post templates, plus idea creation/listing, tag reads, Instagram audio reads, metrics, and channel/account config. Gaps are minor and mostly read-only areas (no tag create/update/delete, no idea update/delete), which agents can largely work around.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data