AutomateLab Content Distribution MCP
Server Details
Publish and schedule content across supported platforms, with publishing state and per-platform adaptation. Built by AutomateLab. Product and documentation: https://automatelab.tech/products/mcp/content-distribution-mcp/
- Status
- Healthy
- Uptime
- 90.9% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: metadata reads (channel_hints, profile_list, subreddit_list) are separated from post lifecycle operations (publish, schedule, drain, status, unpublish). However, post_publish and post_schedule overlap when variants have no schedule_at, since post_schedule also publishes immediately. The descriptions clarify the boundary, but an agent could still hesitate between them.
All names use consistent snake_case and a domain-prefixed convention: post_* for lifecycle operations, and resource_list/resource_hints for metadata. The pattern is predictable, though channel_hints is less action-oriented than the *_list tools and the set is not a strict verb_noun scheme.
Eight tools is well-scoped for a content distribution server. Each tool covers a distinct part of the distribution lifecycle or metadata surface, with no obviously redundant entries.
The set covers profile discovery, channel constraints, subreddit metadata, publishing, scheduling, queue draining, status inspection, and unpublishing. Minor gaps remain: there is no explicit cancel/reschedule operation for queued posts, and profile management is limited to listing. These are workaroundable but slightly limit lifecycle control.
Available Tools
8 toolschannel_hintsStatic per-channel metadataARead-onlyIdempotentInspect
Return static per-channel metadata: character limits, Markdown support flags, tag vocabulary, and CTA placement rules. Side effects: read-only; no external HTTP calls; no auth needed. Fully deterministic — returns compile-time adapter constants. Use channel_hints before composing a variant body to understand channel constraints; use post_publish or post_schedule once you have a valid variant.
Inputs: channel (required). Returns: tag_vocab, max_length, browser_only, cta_placement, +2 more
post_drainFire all scheduled posts due nowAIdempotentInspect
Fire all scheduled posts due at or before the given time boundary. Side effects: makes external HTTP requests for each due entry; writes results to the YAML backend. Idempotent — already-published (content.id, channel) pairs are skipped; no-op when no entries are due. Safe to call from cron. Use post_drain on a recurring schedule to flush the queue; use post_publish or post_schedule to add new content; use post_status to inspect results after drain runs.
Inputs: now. Returns: results
post_publishPublish variants to one or more channels immediatelyAIdempotentInspect
Publish one or more channel variants immediately. Side effects: makes external HTTP requests to each channel platform; writes publish state to the local YAML backend; requires valid credentials in the named profile. Idempotent on (content.id, channel) — re-running with the same IDs returns cached state without re-posting. Use post_publish for immediate-only delivery; use post_schedule when any variant needs a future schedule_at; use post_drain to flush a previously built queue.
Inputs: content (required), variants (required), profile_name (required). Returns: results
post_scheduleSchedule variants for future publishingAIdempotentInspect
Enqueue channel variants with schedule_at for future publishing; variants without schedule_at are published immediately. Side effects: writes entries to the local YAML schedule store; makes external HTTP requests for any immediately-published variants; requires credentials in the named profile. Idempotent on (content.id, channel). Use post_schedule when any variant needs a future publish time; use post_publish for all-immediate delivery; use post_drain to process the scheduled queue later.
Inputs: content (required), variants (required), profile_name (required). Returns: results
post_statusRead publish state for content piecesARead-onlyIdempotentInspect
Return publish state for content pieces. Filters by content_id, channel, or both; returns all entries when neither is given. Side effects: read-only; no external HTTP calls; no auth needed. Deterministic given unchanged backend state. Use post_status to inspect what has been published, what is queued, or what errored; use post_publish, post_schedule, or post_drain to change state.
Inputs: channel, content_id. Returns: results
post_unpublishRetract a published post (best-effort)ADestructiveInspect
Best-effort delete of a published post on the target platform. Side effects: makes an external HTTP DELETE or update request; DEV.to sets published=false (soft delete); platforms without a delete API return success=false without error. Non-idempotent — calling on an already-deleted URL may return a platform 404. Use post_unpublish to retract a live post; use post_status first to obtain the live_url; use post_publish to re-publish after an unpublish.
Inputs: channel (required), live_url (required). Returns: error, success
profile_listList configured distribution profilesARead-onlyIdempotentInspect
Return all distribution profile names configured in the YAML backend. Side effects: read-only; no external HTTP calls. Deterministic given backend state. Use profile_list to discover available profiles before calling post_publish, post_schedule, or subreddit_list; then pass the chosen name as profile_name.
Inputs: no named parameters. Returns: profiles
subreddit_listList Subreddit Catalog entriesARead-onlyIdempotentInspect
Return all subreddits in the Subreddit Catalog with cooldown windows, flair vocabulary, and last-posted metadata. Optionally filtered to subreddits allowed by the named profile. Side effects: read-only; no external HTTP calls. Deterministic given backend state. Use subreddit_list to select a subreddit and obtain flair IDs before composing a reddit: channel variant; pass flair in variant.extras.flair.
Inputs: profile_name. Returns: subreddits
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Social media MCP: publish, schedule & analyze posts on TikTok, Instagram, YouTube, LinkedIn & X
Multi-platform social media post creation, scheduling, and publishing.
Publish and schedule videos to TikTok, YouTube Shorts, Instagram, Facebook, LinkedIn, Pinterest, Bluesky, Threads and X from Claude, Cursor or any MCP client. Upload once, post everywhere, track views in unified analytics, and retry failed posts. Official platform APIs only, free plan available. Docs: https://docs.multi-upload-tool.com/mcp
Publish videos, photos and text to TikTok, YouTube, Instagram, X, LinkedIn and more.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to plan, schedule, and publish Facebook, Instagram, and TikTok posts from AI assistants and any MCP client.MIT
- 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.111,085 npm7MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude Code and Cursor to draft, validate, schedule, and publish posts across Instagram, Threads, LinkedIn, YouTube, X, TikTok and many other platforms, stage media, reply to comments and DMs, and read back post and account analytics. Also exposes automations, an ideas board, and comment/DM tools so an agent can run social accounts end to end from a single self-hosted process.AGPL 3.0

@fopost/mcpofficial
AlicenseAqualityBmaintenanceEnables managing social media posts, accounts, and AI-powered content features from any MCP client, including scheduling, publishing, analysis, and AI caption generation.1430 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.