Social Publisher MCP
Related Servers
Alternatives to Social Publisher MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAutomates video and image-text publishing on Douyin's creator platform using Chrome DevTools Protocol, exposed as MCP tools.80AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceA local MCP adapter collection for social media channels, currently supporting Douyin with tools for channel startup, login assistance, messaging, and notifications.-
- FlicenseBqualityCmaintenanceMCP server wrapping social-auto-upload CLI for AI clients to verify cookies and publish videos/notes to Chinese social platforms (Douyin, Kuaishou, Xiaohongshu, Bilibili).10-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables controlled Xiaohongshu content publishing with an immutable review workflow, requiring explicit human confirmation before any release. It supports content generation, local editing, compliance recall, and one-time authorized posting, defaulting to generate-only mode.Apache 2.0
- FlicenseAqualityCmaintenanceA local MCP server that enables Douyin keyword search and comment campaigns through the user's own logged-in Chrome, with human approval, cross-campaign deduplication, and resume after manual verification.11-
- AlicenseBqualityBmaintenanceMCP server for governed AI content publishing to platforms like WeChat, Juejin, CSDN, and Zhihu, exposing tools for platform auth checks, content preflight, publish job lifecycle, verification, and liveness monitoring.8MIT
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of the social publishing workflow: platform enumeration, auth management, post preparation, publishing, and status retrieval. Even the two auth-related tools are clearly separated by their actions (starting a login vs. checking existing auth state).
All tool names follow a consistent verb_noun pattern in snake_case (list_platforms, login_platform, check_platform_auth, prepare_post, publish_post). The slight variation in check_publish_status still adheres to the same style and is easily readable.
With six tools, the server is well-scoped for its purpose, covering the essential operations of platform discovery, authentication, post preparation, publishing, and status checking without unnecessary redundancy or bloat.
The core lifecycle is covered: login/check auth, prepare, publish, and check status. Minor gaps exist, such as no logout or auth refresh operation and no list of previously published posts, but these are not critical to the main publishing workflow and can be worked around.