Ready
One control plane for every content agent, site, and draft.
Connect evidence, agent work, durable drafts, human review, search operations, and CMS destinations without handing the whole stack to an agent.
Content control loop
Illustrative product schematicBlogFactory · Editorial control schematics
Evidence enters. A reviewed CMS draft leaves.
Scoped
MCP agent
Research · create · reviseWorking
BlogFactory draft
Versioned workRequired
Human review
Preflight · destinationDraft only
CMS draft
Never live publishEvidence readRevision trackedApproval explicitDelivery idempotent
Move faster without losing editorial control.
One operating loop
Sources, agent work, review, and destination state stay connected.
A workspace per site
Content, context, permissions, search evidence, and CMS destinations remain site-scoped.
Decisions stay human
Editors see revisions and blockers before an approved CMS draft handoff.
Work stays inspectable
Runs, queue state, and sanitized operation history show what happened next.
A durable workspace for every draft.
See source, writer profile, model, lifecycle state, and SEO readiness without reconstructing the work from agent conversations.
- Search and filter the inventory
- Open the current draft and revision
- Keep delivery state visible
Connect agents to one authorized site.
The MCP work layer receives useful, scoped authority while the web layer keeps connection status and boundaries visible.
- OAuth or personal token
- Current catalog discovered live
- Credentials never returned
Turn evidence into the next reviewed move.
Search Growth keeps complete-day provenance beside the opportunity and the action it can create.
- Page and query evidence
- Reviewable next action
- No ranking guarantee
From evidence to a reviewed CMS draft.
Connect site context
Add sources, Search Console, brand knowledge, provider access, and a destination.
Let agents do the work
Research, generate, diagnose, and revise through a compatible MCP client.
Review and deliver
Resolve blockers, approve the current version, and send it to the selected CMS as a draft.
Built for controlled content operations.
Work layer
Agents operate through scoped tools, not shared publishing credentials.
- MCP-compatible clients
- Draft generation and revision
- Search diagnosis
- Site-scoped permissions
Control layer
The web app keeps summaries, queues, settings, and exceptions visible.
- Content inventory
- Review and preflight
- Run monitoring
- Sanitized audit
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.