The BlogFactory platform

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.

View on GitHub Self-host BlogFactory

MCP work layer · Web control layer · CMS draft boundary

Content control loop

Illustrative product schematic

BlogFactory · Editorial control schematics

Evidence enters. A reviewed CMS draft leaves.

Ready

Sources

RSS · briefs · search

Scoped

MCP agent

Research · create · revise

Working

BlogFactory draft

Versioned work

Required

Human review

Preflight · destination

Draft only

CMS draft

Never live publish

Evidence readRevision trackedApproval explicitDelivery idempotent

Why BlogFactory

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.

Operate

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

BlogFactory content inventory filtered across drafts and published items — Product capture · August 23, 2026. Values shown belong to the captured workspace.

Control

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

BlogFactory MCP Connections showing site-scoped authorization and agent workflow — Product capture · August 23, 2026. Catalog count is shown at capture time; clients discover the current catalog live.

Grow

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

BlogFactory Search Growth overview with complete-day provenance and next best action — Product capture · August 23, 2026. Values shown belong to the captured workspace.

How it works

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.

Capabilities and boundaries

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

FAQ

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.

Can I self-host BlogFactory now?

Yes. The public repository is available for self-hosting as a release candidate. BlogFactory Cloud is not available yet.

Run BlogFactory where your content operation lives.

Inspect the public source, then follow the source-build Docker Compose guide for the open-source release candidate.