Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Upload-Post

No user-submitted related servers found.

    Related Servers

    • QPost MCP

      arslan2012
      A
      license
      A
      quality
      C
      maintenance
      MCP server for QPost that lets AI agents schedule and publish video/image posts to YouTube, TikTok, and Instagram via QPost's REST API.
      7
      36 npm
      MIT

    • Ravenpost MCP server

      target1m
      A
      license
      Not graded
      quality
      B
      maintenance
      A hosted MCP server that lets AI assistants schedule and publish social media posts across Instagram, TikTok, X, LinkedIn, YouTube, Pinterest, Facebook, Telegram, Threads, and Bluesky. It provides tools for managing accounts, posts, media, and analytics, including post previewing before publishing.
      1
      MIT

    • Outpost

      andrezani
      A
      license
      Not graded
      quality
      C
      maintenance
      Social media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.
      64 npm
      MIT

    • social0-mcp

      Abhishek-B-R
      A
      license
      A
      quality
      B
      maintenance
      MCP server to manage social media accounts from AI assistants, enabling post creation, scheduling, publishing, and media uploads across multiple platforms.
      13
      13 npm
      1
      MIT

    • postfast-mcp

      peturgeorgievv-factory
      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
      920 npm
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 57 tools

    Disambiguation3/5

    Most tools are distinct, but there are several overlapping pairs: get_status vs get_job_status, get_analytics vs get_post_analytics vs get_cached_post_analytics vs get_total_impressions, and reply_to_comment vs public_reply_to_comment vs create_comment vs send_dm. The descriptions help, but an agent could easily pick the wrong analytics or comment tool.

    Naming Consistency4/5

    The set mostly follows a verb_noun pattern (upload_photos, list_scheduled, get_analytics, delete_comment, cancel_scheduled). Minor deviations exist: tiktok_music_trending and tiktok_music_search are noun-first rather than verb-first, and get_google_business_locations is a bit verbose, but the overall pattern is consistent and readable.

    Tool Count2/5

    57 tools is a very large surface for a single MCP server. While the domain is broad (publishing, scheduling, analytics, comments, DMs, FFmpeg processing, user management), the count is heavy and includes internal/app staging helpers (get_media_upload, delete_media_upload) that add clutter. The scope could be split into separate servers.

    Completeness4/5

    The publishing lifecycle is well covered: create, schedule, retry, status, history, cancel, edit, unpublish. Analytics, comments, DMs, and queue management are also present. Minor gaps exist: no tool to update a published post, no tool to list failed uploads specifically, and Reddit is explicitly unavailable, but the core workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources