Content Distribution MCP
Related Servers
Alternatives to Content Distribution MCP
- AlicenseAqualityCmaintenanceAutomateLab n8n MCP helps AI agents generate and lint workflows, diagnose failed executions, and manage live n8n instances. Product and documentation: https://automatelab.tech/products/mcp/n8n-mcp/12107 npm14MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceCampaign-driven social engagement MCP server for authentic developer community interaction (Dev.to, Bluesky, Twitter, Reddit) with a streamlined scout-draft-strike pipeline minimizing LLM round trips.MIT
- AlicenseAqualityCmaintenanceCross-publishes a single markdown draft to 5 CMS platforms (dev.to, Hashnode, Ghost, WordPress, Medium) and 4 social networks (Bluesky, Mastodon, LinkedIn, X) from any MCP client, with built-in SEO scoring, schema.org JSON-LD, and canonical URL handling so cross-posts compound search rankings instead of competing.2967 npm5MIT
- FlicenseAqualityDmaintenanceAn MCP server that formats and syndicates Markdown content to Twitter/X, Threads, and a static blog on S3, with automatic thread splitting and preview capabilities.3-
- AlicenseNot gradedqualityCmaintenanceSocial media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.9 npmMIT
- AlicenseAqualityAmaintenanceSchedule and manage social media posts across 13 platforms (Bluesky, Threads, Instagram, LinkedIn, Mastodon, YouTube, Facebook, Pinterest, Telegram, Nostr, X/Twitter, Discord, Tumblr and more). OAuth 2.0 + PKCE, 10 tools, draft-first workflow for AI agents.1017AGPL 3.0
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that repurposes text or URL content into platform-optimized posts for Twitter, LinkedIn, Instagram, and newsletters using AI. It enables users to automatically transform articles and blog posts into engagement-ready social media threads and professional captions.-
TDQS
Scored across 8 tools
Each tool maps to a distinct action or data source, and descriptions explicitly distinguish publish, schedule, drain, status, and unpublish flows. No two tools appear interchangeable.
The five mutating/state tools use a clear post_* prefix, but the read-only metadata tools use noun-first names such as profile_list, subreddit_list, and channel_hints. This creates two naming families, though the overall scheme remains readable and mostly predictable.
Eight tools is well-scoped for a content-distribution workflow covering immediate publishing, scheduling, queue draining, status inspection, unpublishing, and channel/profile discovery. No tool feels redundant.
Core lifecycle is covered: publish, schedule, drain, status, unpublish, plus profile, channel, and subreddit metadata. Notable gap: no explicit cancel or edit operation for scheduled queue entries, and no content-listing tool, though most workflows can work around these.