Skip to main content
Glama

Related Servers

Alternatives to Social Publish MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Schedule and manage social media posts across 10 platforms (Instagram, Facebook, TikTok, X, LinkedIn, YouTube, Threads, Pinterest, Bluesky, Telegram) from any MCP-compatible AI assistant. Supports batch posting, media uploads, analytics, and platform-specific features like Reels, Shorts, and carousels.
      11
      412 npm
      7
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Upload-Post is the all-in-one social media MCP server the Model Context Protocol server for social media publishing, scheduling and analytics. Connect any MCP-compatible AI agent (Claude, Cursor, ChatGPT, Claude Desktop, n8n, and more) and publish, schedule and analyze content across 13+ social networks from one API: TikTok, Instagram, YouTube, YouTube Shorts, Instagram Reels, LinkedIn, Facebook
      72
      558 npm
      13
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to list platform login status and rules, preview posts, and publish text, images, or video to X, LinkedIn, YouTube, Facebook Pages, Instagram, and TikTok from one MCP interface. Each post is validated against per-platform rules before publishing, which requires explicit confirmation.
      3
      MIT

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role: publish for one post, publish_batch for multiple jobs, check_accounts for login detection, status for connection/job state, and history for past results. The only mild overlap is publish vs publish_batch for a single job, but the batch description clearly frames it as multi-post execution with all-or-nothing validation.

    Naming Consistency3/5

    Mostly readable, but conventions are mixed: publish and publish_batch are verb-based, check_accounts is verb_noun, while status and history are bare nouns. The names are predictable enough to use, but do not follow a single consistent pattern.

    Tool Count5/5

    Five tools is well-scoped for a social publishing server: one core action, a batch variant, account validation, connection status, and history. Each tool clearly earns its place without redundancy.

    Completeness3/5

    Core publishing, scheduling, batching, account checks, status, and history are covered. However, there is no explicit cancel/delete or list-scheduled-posts operation, which are notable gaps for a toolset that supports scheduling, forcing agents to work around via browser tabs or history.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing