MCP SERVER · OFFICIAL PROJECTPublish one piece of writing to DEV.to, Hashnode, GitHub Discussions, Reddit and Bluesky in per-channel variants — idempotent, schedulable, with subreddit cooldowns respected.
LABSCO SUMMARY
Idempotency on the content id and channel pair is the feature that makes this safe to hand to an agent: a run that dies halfway can simply be run again, and the pairs that already went out are skipped rather than duplicated. The division of labour is deliberate too — it hands back each channel's limits and tag vocabulary and leaves the rewriting to you, which is why three channels it cannot authenticate against return a compose URL instead of pretending to publish.
A distribution layer, not a writer. Your agent produces the variant for each channel; this server publishes them, tracks what went where in a local store, and enforces the platform rules — character limits, tag vocabularies, subreddit cooldowns. It makes no model calls of its own.
Credentials live in a distribution profile at ~/.distribution-mcp/profiles.yaml, and only for the channels you actually use: DEV_TO_API_KEY for DEV.to; HASHNODE_TOKEN with HASHNODE_PUBLICATION_ID; GITHUB_TOKEN with GITHUB_DISCUSSION_REPO; REDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_USERNAME and REDDIT_PASSWORD; BLUESKY_IDENTIFIER with BLUESKY_PASSWORD. LinkedIn, Medium and Twitter/X take no credentials at all — those channels answer with needs_browser and a compose URL for you to finish by hand. It starts over stdio as npx -y @automatelab/content-distribution-mcp, and the same YAML backend holds the schedule and publish state. Tool names were renamed in v2.2.0 from flat names (publish, schedule) to prefixed ones (post_publish, post_schedule), so older prompts and n8n nodes that use the flat names need updating.
One command plus a key — npx @automatelab/content-distribution-mcp, then supply credentials
USE CASES
Send the per-channel variants in one call; each publishes under the profile's credentials, and re-running skips whatever already went live.
Queue the variants with their times, then let a cron job fire everything that has come due; variants with no time set go out immediately.
Read the channel's character limit, Markdown support, tag vocabulary and call-to-action rules first, so the variant fits rather than being truncated on arrival.
Check the catalogue for each subreddit's cooldown window, required flair and when it was last posted to, filtered to what your profile is allowed to touch.
Read the publish state for the content id or the channel; the call touches nothing external and needs no credentials.
Request removal on the platform, knowing that DEV.to switches the post back to draft and platforms without a delete API report that it could not be done.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
channel_hintsReturn 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.
post_drainFire 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.
post_publishPublish 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.
post_scheduleEnqueue 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.
post_statusReturn 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.
post_unpublishBest-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.
profile_listReturn 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.
subreddit_listReturn 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.
BEFORE YOU INSTALL
8 tools when we connected. Tool names use underscores (post_publish, channel_hints), not the flat names (publish, schedule) used before v2.2.0 and still shown in docs/PIPELINE.md.
CONTEXT COST
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx @automatelab/content-distribution-mcp{
"mcpServers": {
"content-distribution": {
"command": "npx",
"args": [
"-y",
"@automatelab/content-distribution-mcp"
]
}
}
}The blocks carry no credentials: the server reads them from a distribution profile at ~/.distribution-mcp/profiles.yaml, under default: credentials:. Set only the channels you intend to use — LinkedIn, Medium and Twitter/X need none.
npx -y @automatelab/content-distribution-mcpThe blocks carry no credentials: the server reads them from a distribution profile at ~/.distribution-mcp/profiles.yaml, under default: credentials:. Set only the channels you intend to use — LinkedIn, Medium and Twitter/X need none.
MCP servers
gomessoaresemmanuel-cpu
chrismole310
olamide-olaniyan