Deliver the approved version to the right CMS draft.
Require the current version, a valid preflight, explicit approval, and a selected destination before a draft leaves BlogFactory.
Connection topology
Illustrative product schematicBlogFactory · Editorial control schematics
Every connection stays attached to a site.
Connection boundary · Site 01
Make the last mile deliberately boring.
Confirm readiness
Block delivery when required metadata, permissions, or destination state is missing.
Select the destination
Choose the exact CMS connection instead of relying on an implicit default.
Protect current work
Expected-version checks reject stale approvals.
Retry safely
Idempotency protects against accidental duplicate draft delivery.
The handoff starts with the current revision.
Warnings and blockers remain visible before any destination action is available.
- Version-aware review
- Destination readiness
- Editorial decision
Connections stay attached to the active site.
Operators can test and manage CMS connections before selecting one for a reviewed draft delivery.
- WordPress, Ghost, Wix, and Framer
- Connection health
- Site-scoped credentials
A narrow path from approval to CMS draft.
Review preflight
Read the current revision and resolve blockers.
Choose and approve
Select the exact destination and confirm the handoff.
Create CMS draft
Deliver the approved version once and retain the result.
Built for controlled content operations.
Before delivery
The review packet is the source of truth.
- Revision current
- SEO and metadata ready
- Permission confirmed
- Destination healthy
After delivery
MCP authority ends at a recoverable CMS state.
- Draft only
- No delete
- Idempotent result
- Sanitized operation event
Before you connect.
Does BlogFactory keep sites separate?
Yes. Content, sources, permissions, provider access, search properties, and destinations remain scoped to the authorized site.
Can an MCP agent publish live or delete content?
No. Agent authority stops at approved CMS draft creation. Live publishing, deletion, credentials, and account administration stay outside MCP.
How can I use BlogFactory?
Self-host the AGPL-3.0-only release candidate for free, or create a managed BlogFactory Cloud account from $5 per month. Both editions keep CMS delivery draft-only.
Run BlogFactory where your content operation lives.
Inspect the public source, then follow the source-build Compose guide — or let Cloud run it from $5 a month. The boundary is identical in both.