Content Distribution MCP

Why STEADY

STEADY (74) for a focused, agent-native tool that solves a concrete distribution workflow with two design decisions that matter — idempotency on (content_id, channel) and a no-LLM-in-server split — clearly evidenced on the surface, MIT-licensed and npx-installable with eight documented MCP tools. Not higher because the actual publish/idempotency/retry behaviour and the anti-spam rules can't be verified from the public page, four of eight channels still require a human paste step, and it's a young single-maintainer project with adoption unproven. Not FADING because the tool surface, tool contract and honest scoping show real, thoughtful engineering.

Public-surface checklist

• PASS Homepage loads (required)
• PASS Primary value prop (required) — A genuinely agent-native content-distribution MCP: your agent writes the copy, t
• PASS Cta present
• PASS Evidence or demo — 1 screenshot(s) captured

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-d14a0c28698f9b6a-automatelab-tech). Our own captures — not vendor marketing material.

×

←→

What it does well

• Eight namespaced MCP tools (post_publish/schedule/drain/status/unpublish, channel_hints, profile_list, subreddit_list) with a clear one-envelope-plus-variants contract
• Idempotent on (content_id, channel): a re-run of the same envelope is a no-op — no double-posts or duplicate Reddit threads (as stated)
• Zero LLM calls in the server: host supplies copy/credentials/decisions, MCP supplies I/O — model- and host-agnostic
• npx -y install with one JSON block, Node 18+ only; works over stdio or SSE against Claude Code, Cursor, n8n and the plain mcp client
• Honest tiering of channels (AUTO vs MANUAL) instead of pretending every platform has a usable API; dual YAML-local / Notion-team backend

What it fails at

• Four of eight channels (Reddit, Medium, LinkedIn, Twitter) are MANUAL — a human still pastes and clicks Publish; not fully autonomous distribution
• Idempotency, retry and anti-spam/subreddit-cooldown behaviour are design claims that can't be exercised or verified from the public surface
• Young, single-maintainer project (@ratamaha); adoption, maintenance cadence and long-term platform-API resilience are unproven on the surface
• unpublish is best-effort only (Reddit is honor-system, browser channels operator-driven)

Pricing & access

• ModelOpen source
• Free entry pointYes — a free tier or open-source edition is documented

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-21.

Compared to

• Zapier agent-native-mcp-vs-hosted-no-code-automation

  Zapier is a mature hosted automation platform with a GUI, huge app catalog and managed reliability; Content Distribution MCP is a narrow, code-first MCP server that an AI agent drives directly, with idempotency and canonical-URL handling built for developer-community channels specifically. Choose Zapier for breadth and a no-code UI, this for agent-native, MIT-licensed, tokens-you-control publishing.

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 63/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

First-class MCP server (npx @ratamaha/content-distribution-mcp) exposing eight tools over stdio or SSE; any MCP host (Claude Code, Cursor, n8n, plain mcp client) drives publishing directly. No LLM calls in the server, so behaviour is deterministic and directly testable given channel credentials. A genuine agent-to-agent distribution surface.

Agent-friendly score: 9/10

Evidence

• MCP server publishing one piece of content to eight developer-community channels, MIT-licensed, npx @ratamaha/content-distribution-mcp — source (2026-08-21) verified
• Eight MCP tools namespaced by domain (post_publish/schedule/drain/status/unpublish, channel_hints, profile_list, subreddit_list) — source (2026-08-21) verified
• Idempotent on (content_id, channel); re-running the same envelope is a no-op — source (2026-08-21) verified
• Zero LLM calls in the server; works with any model/host over stdio or SSE (Claude Code, Cursor, n8n, mcp client) — source (2026-08-21) verified
• Three publish tiers: six AUTO native-API channels, remaining channels MANUAL draft+compose-URL — source (2026-08-21) verified