content-publish-engine-mcp
This server is an automation engine for publishing finalized articles to external platforms (WeChat, Juejin, CSDN, Zhihu) and managing their full publication lifecycle—without generating or editing content.
Check platform authentication with
platform_auth_probewithout exposing credentials.Preflight content with
publish_content_preflightagainst official platform rules before publishing.Create idempotent publish jobs with
publish_job_create, including optional scheduling, tagging, and categorization.Run publish jobs immediately or on schedule with
publish_job_run.Retrieve job status and details with
publish_job_get.Verify publication and resolve public URLs with
publish_job_verify.Check article liveness with
publish_liveness_checkand manage lifecycle states (provisional, stable, rejection, timeout, removal detected).Check verification due with
publish_verification_duebased on the next verification timestamp.
It also supports third-party platform adapters, an HTTP API for job management and system monitoring, durable audit events and webhooks, JSON/SQLite storage, and an authenticated loopback bridge for real platform execution.
Provides publishing tools for the CSDN platform, including preflight checks, publish job creation and execution, and verification via an authorized local bridge or custom transport. Supports mock and real modes.
Provides publishing tools for the Juejin platform, including preflight checks, publish job creation and execution, and verification via an authorized local bridge or custom transport. Supports mock and real modes.
Provides publishing tools for the WeChat platform, including preflight checks, publish job creation and execution, and verification via an authorized local bridge or custom transport. Supports mock and real modes.
Provides publishing tools for the Zhihu platform, including preflight checks, publish job creation and execution, and verification via an authorized local bridge or custom transport. Supports mock and real modes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@content-publish-engine-mcp Preflight my WeChat draft and show official rule coverage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
content-publish-engine
An automation engine that takes a completed article, publishes it to external platforms, discovers the public URL, and keeps verifying that the article remains live.
It deliberately does not generate, rewrite, plan, or score content. Your CMS, editor, AI agent, or Markdown workflow owns the article; this engine owns reliable publication.
Publishing lifecycle
completed article -> scheduled job -> authenticated publish -> platform acceptance
-> public URL discovery -> provisional public observation
-> 24h check -> 72h stable publication -> removal detectionUnlike draft-sync tools, a successful job means the engine performed the publish action and entered verification. Draft creation alone is not treated as publication.
Related MCP server: mcp-server-wechat-mp
Included capabilities
Adapter registry for WeChat Official Account, Juejin, CSDN, Zhihu, and third-party plugins.
Idempotent jobs, content hashes, platform write locks, worker leases, and duplicate protection.
Immediate and scheduled publication through one
PublishOrchestrator.Read-only verification that never repeats an ambiguous publish action.
Public URL discovery, verification backoff, 24/72-hour survival checks, stable publication, rejection, timeout, and removal states.
JSON and SQLite repositories plus a distributed lock/repository contract.
Long-running worker, MCP server, HTTP API, and authenticated local bridge.
Webhook events, durable audit events, and in-process telemetry primitives.
Versioned official-rule registry with source metadata.
Generic asset resolution/upload contracts.
Versioned browser-selector bundles and structure-change detection.
An included WeChat Official Account executor using the official draft and free-publish APIs.
Requirements
Node.js 22.5 or newer. Node 24 LTS is recommended.
npm ci
npm run checkSDK
import {
PublishOrchestrator,
SqlitePublishRepository
} from "content-publish-engine/publish-engine";
const repository = new SqlitePublishRepository(".data/publish.db");
const engine = new PublishOrchestrator({ repository });
const { job } = await engine.createJob({
jobId: "request-42",
platform: "wechat",
article: {
sourceId: "cms-article-42",
title: "A completed article",
markdown: "<p>Final HTML or Markdown body</p>",
scheduledAt: new Date().toISOString()
}
});
await engine.runPublishJob(job.id);Runtime entry points
npm run mcp:start
npm run http:start
npm run worker:start
npm run bridge:startThe worker processes due verification jobs before new publish jobs. SQLite is the default runtime repository; set PUBLISH_REPOSITORY=json for low-volume local JSON storage.
HTTP endpoints:
POST /v1/jobsGET /v1/jobsGET /v1/jobs/:idPOST /v1/jobs/:id/runPOST /v1/jobs/:id/verifyPOST /v1/run-dueGET /v1/reliabilityGET /v1/telemetry
MCP tools include platform discovery/auth, preflight, job creation/execution/read-only verification, due-job execution, liveness checks, and reliability metrics.
Real platform execution
The built-in transport calls an authenticated loopback bridge:
PUBLISH_ENABLED=true
PUBLISH_BRIDGE_URL=http://127.0.0.1:9528
PUBLISH_BRIDGE_TOKEN=replace-with-a-local-secretThe repository includes a WeChat Official Account executor. Other platforms use the same plugin and transport contracts and require an authorized executor supplied by the operator. The project never ships account cookies or attempts to bypass CAPTCHA or risk controls.
Before the first live write, record the operator's explicit authorization locally:
npm run authorize -- wechat operator-nameThe authorization record contains no platform credential and is ignored by Git through .data/.
For the included WeChat executor, also set WECHAT_APP_ID and WECHAT_APP_SECRET, start the bridge, then run the worker or call the HTTP/MCP run endpoint. The executor creates the official draft when needed, submits the free-publish action, and queries the same task for its public URL; it never treats draft creation as successful publication.
See adapter guide, official rule policy, and live authorization.
Storage and scale
JSON: single-process local use.
SQLite: durable local service with WAL and transactional claims/locks.
Distributed deployments: implement
PublishRepositoryandDistributedLockProviderwith your database and lock service.
License
Available Tools
8 toolsplatform_auth_probeA
Check whether a platform adapter is authenticated without returning credentials.
Inputs: platform (required).
publish_content_preflightA
Check publish-payload completeness and verified official platform rules without applying editorial preferences.
Inputs: title (required), markdown (required), platform (required), tagIds, +2 more.
publish_job_createB
Create an idempotent publish job from a final draft. Returns a durable job handle.
Inputs: title (required), markdown (required), platform (required), tagIds, +4 more.
publish_job_getA
Read one publish job and its current status from the local job store.
Inputs: jobId (required).
publish_job_runB
Execute one publish job by calling the platform adapter directly. Returns the publish result.
Inputs: jobId (required).
publish_job_verifyA
Verify a previously submitted publish job and resolve its public URL.
Inputs: jobId (required).
publish_liveness_checkB
Check whether an observed public article is still live and advance its lifecycle state.
Inputs: jobId (required), schedule.
publish_verification_dueB
Check whether a publish schedule is due for verification based on its nextVerificationAt.
Inputs: nextVerificationAt (required), now.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools target distinct actions (preflight, create, run, get, verify, liveness, due-check, auth-probe). However, publish_liveness_check and publish_job_verify both involve verifying published state, which could cause confusion despite differing contexts.
Naming is inconsistent: publish_job_create/run/get/verify follow verb_noun, but publish_liveness_check, publish_verification_due, and publish_content_preflight are noun phrases, and platform_auth_probe breaks the publish_ prefix. This mixed pattern reduces predictability.
With 8 tools, the set is well-sized for a content publishing engine, covering the main workflow without being bloated. Each tool addresses a clear step in the process.
Core lifecycle (preflight, create, run, verify, liveness) is covered, enabling end-to-end publishing. Minor gaps exist: no job deletion/listing or schedule management, but these are not essential for the stated purpose.
Maintenance
Related MCP Connectors
MCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram.
Hosted MCP server for AI agents to post to LinkedIn profiles and X and upload to YouTube.
Agent-first social media publishing, scheduling, analytics, and unified inbox API + 16-tool MCP server across 18 social platforms (X, LinkedIn, Instagram, YouTube, TikTok, Threads, Bluesky, Reddit, Telegram, Discord, Mastodon, Facebook, Pinterest).
Blog MCP server for AI agents. One signup call returns a blog, an API key and a live URL; then your agent publishes markdown posts and gets public URLs back. Your agent does the writing; you get a dashboard for stats.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI tools to automatically publish articles to WeChat Official Accounts, supporting Markdown-to-HTML conversion, image handling, and both preview and official publishing modes.262MIT
- AlicenseAqualityFmaintenanceEnables AI agents to publish articles to WeChat Official Account (微信公众号). Supports image upload, draft creation, and publishing via standardized MCP protocol.51ISC
- AlicenseAqualityDmaintenanceA local MCP service for safely preparing, validating, and executing multi-platform social media auto-publishing, with dry-run mode and real adapter for Douyin.61MIT
- FlicenseBqualityDmaintenanceMCP server wrapping social-auto-upload CLI for AI clients to verify cookies and publish videos/notes to Chinese social platforms (Douyin, Kuaishou, Xiaohongshu, Bilibili).10-