Social Publish MCP
Related Servers
Alternatives to Social Publish MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceSchedule 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.11412 npm7MIT
- AlicenseAqualityBmaintenanceEnables MCP clients like Claude or Cursor to upload videos from your local machine directly to YouTube, schedule them, and manage channel content through Runsheet.11123 npmMIT

Upload-Postofficial
AlicenseBqualityAmaintenanceUpload-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, Facebook72558 npm13MIT- AlicenseBqualityBmaintenanceEnables AI agents to control a YouTube channel end-to-end by uploading videos, editing metadata, managing playlists, moderating comments, and reading analytics through MCP tools.20MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to publish social posts and Reddit comments to connected platforms by executing jobs in the user's own logged-in desktop Chrome session, with OAuth and without platform API keys.MIT
- AlicenseAqualityCmaintenanceEnables 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.3MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.