Skip to main content
Glama

Related Servers

Alternatives to Buffer MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents and clients to discover accounts and channels, read scheduling and analytics data, and manage posts, content items, and templates through 41 GraphQL-backed tools with private credential profiles and confirmation-gated mutations.
      41
      41 npm
      AGPL 3.0
    • 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 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
      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.
      187 npm
      106
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to schedule social media posts, create videos and carousels, manage content sources and connected accounts, and read analytics and revenue attribution data from a social scheduling account. It supports hosted remote connections via browser sign-in or scoped API keys, plus local and self-hosted deployments with 49 tools.
      49
      190 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource and action (buffer_get_channel vs buffer_list_channels, buffer_get_post vs buffer_create_post). Minor overlap exists between media_probe and media_preflight (both validate media) and between cloudinary_upload and cloudinary_upload_batch, but descriptions clarify the single-vs-batch and URL-vs-channel-rule distinctions. An agent can reliably select the right tool.

    Naming Consistency4/5

    Predictable verb_noun pattern with consistent domain prefixes (buffer_, cloudinary_, media_). Verbs (get/set/list/create/update/delete/upload) are used consistently. Minor deviations: cloudinary_link and cloudinary_variants omit a trailing noun, and buffer_get_analytics/buffer_list_daily_limits slightly break the resource_verb pattern, but overall readable and consistent.

    Tool Count3/5

    23 tools is on the heavy side, spanning config, posts, media, analytics, and ideas domains. Each tool earns its place within its sub-domain, but the surface is large enough that it borders on overwhelming for a single server. Reasonable but at the upper edge of comfortable scoping.

    Completeness4/5

    Posts have full CRUD, config is fully manageable, and media/Cloudinary lifecycle is covered. Gaps: ideas only support list/list-groups/create with no update or delete, analytics is read-only, and channel management is read-only. These are minor gaps agents can work around for core Buffer workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues