Connect agents, sources, Search Console, models, and CMS destinations.
Build one site-scoped operating loop from the tools you already use without moving provider or publishing credentials into an agent conversation.
Connection topology
Illustrative product schematicBlogFactory · Editorial control schematics
Every connection stays attached to a site.
Connection boundary · Site 01
Connect the loop, not another disconnected tool.
Bring in evidence
Use RSS, batch import, campaigns, and Search Console context.
Work through MCP
Connect compatible agent clients to the authorized site.
Choose the destination
Route approved work to WordPress, Ghost, Wix, or Framer as a draft.
Keep connections scoped
Credentials, sources, properties, and destinations stay attached to one site.
Test and manage destinations per site.
The captured operator surface shows a connected destination and available CMS integrations. MCP delivery still requires explicit approval and stops at draft creation.
- Connection health
- Site-scoped credentials
- Explicit destination
A bounded connection path for every site.
Select a site
Start with the workspace that owns the context and destination.
Connect the stack
Add agent, search, source, model, and CMS access as needed.
Test before delivery
Verify the connection and select the destination explicitly.
Built for controlled content operations.
Inputs and intelligence
Bring evidence into one scoped workspace.
- RSS and batch import
- Google Search Console
- OpenRouter, OpenAI, and Google services
- Site context
Agents and destinations
Connect work to controlled draft handoff.
- MCP-compatible clients
- WordPress and Ghost
- Wix and Framer
- Draft-only MCP 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.