x-publisher-mcp

Overview

An MCP tool for social content distribution with a strict human-approval gate. Content enters a queue; nothing leaves until a human approves it. The tool executes the distribution; it never decides to post. Integrated with the article-drafting pipeline from day one — designed as part of the publishing flow, not wired in after the fact.

Problem

Automated social posting tools optimise for throughput. Queue something and it goes. That model trades control for speed — acceptable for scheduled marketing content, wrong for editorial output where accuracy and timing carry real weight.

The gap is a distribution layer that gives the pipeline the ability to queue and route content across platforms, while keeping the final action human. Remove the approval gate and you have an autonomous poster. Keep it and you have infrastructure that a human operates.

Solution

Built as an MCP tool that sits at the end of the article-drafting pipeline:

• Queue — content from the pipeline lands in a structured queue with platform target, copy, and metadata
• Human approval gate — nothing executes without explicit approval; the tool surfaces the queued item and waits
• Execute on approval — distribution fires immediately on approval; no lag, no requeue
• Never autonomous — the constraint is architectural, not just a config flag. The tool has no code path for unattended posting.

The integration with the article-drafting MCP was built on day one. The pipeline produces content; x-publisher-mcp is where that content meets distribution. Bolting a distribution layer onto a pipeline after the fact creates mismatches in metadata, timing, and approval flow — doing it at design time avoids all of that.

Tech Stack

Outcome

Integrated with the editorial pipeline from launch. Human approval gate proven in production. Zero autonomous posts — by design, not by accident.