Built an MCP server for multi-channel content publishing - idempotent by design, with Reddit pre-flight checks before any API call

One problem with agent-driven publishing: side effects are hard to make reliable. An agent calls publish, the network drops at channel 4 of 8, and now you don't know what landed. content-distribution-mcp is designed around that constraint. Every publish call is idempotent on (content\_id, channel). The server tracks state in a backend (YAML or Notion) and skips channels that already succeeded. A retry is always safe — the agent can call publish again without checking what completed. The Reddit pre-flight is the other interesting piece from an agent reliability standpoint. Reddit's moderation is probabilistic and account- damaging if you get it wrong. Rather than let the agent fire and hope, the server runs all checks locally first: \- Cooldown per subreddit \- 5/day global submission cap \- Self-promo ratio for the subreddit \- Required flair presence If any check fails, the tool returns a structured error with the reason. The agent gets a clear signal, not a silent moderation removal days later. The server makes zero LLM calls. The agent layer handles copy generation; the server handles I/O, state, and error recovery. Clean separation. 8 channels: DEVto, Hashnode, GitHub Discussions, Bluesky, Reddit, Medium, LinkedIn, Twitter. pip install content-distribution-mcp