See real work first
Prioritize blockers, changes requested, review, stale approval, and warnings.
Every draft, blocker, revision, and approval in one queue.
Make human review concrete with current-version context, preflight, warnings, explicit destination selection, and conflict-safe delivery.
Review workspace
Illustrative product schematicBlogFactory · Editorial control schematics
One queue for blockers, revisions, and approval.
Review Queue3 require action
Snippet refreshRevision readyReview
Evergreen guideSEO field missingBlocker
Weekly briefDestination confirmedApprove
Preflight
Ready for CMS draft
- ✓ Revision current
- ✓ Destination selected
- ✓ SEO fields complete
Ghost · Primary publicationApprove draft delivery
Review the decision, not a mystery draft.
Know what changed
Revision summaries make review concrete before approval.
Catch delivery blockers
SEO, image, metadata, permission, and destination checks run before handoff.
Prevent stale writes
Optimistic locking rejects outdated edits instead of overwriting current work.
The current revision carries its delivery readiness.
Review the saved revision, canonical SEO, destination, cover image, publishing metadata, and editorial state before handoff.
- Current revision visible
- Blockers and warnings separated
- Preview and history one click away
One review path in the web app or MCP client.
Open the review packet
Read the current revision, summary, state, permissions, and destination readiness.
Resolve blockers
Complete missing SEO, image, metadata, and routing requirements.
Approve current version
Confirm the destination and deliver an idempotent CMS draft.
Built for controlled content operations.
Review surfaces
The Review Queue and MCP Review Card use the same control-plane services.
- Revision summary
- Shared preflight
- Warnings and blockers
- Destination readiness
Delivery guarantees
Final handoff is narrow, explicit, and safe to retry.
- Expected version required
- Destination selected explicitly
- Approval required
- Idempotent delivery
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.