BlogFactory
io.blogfactoryPublished by blogfactory.ioOfficial publisherv0.5.1Updated Nov 4, 2026
Agent control plane for multi-site content ops: research, drafts, review, CMS draft delivery.
Overview
BlogFactory is a remote, OAuth-protected MCP control plane for multi-site content operations: research, drafts, revisions, review, and CMS draft delivery.
- What you can do
- Work with source evidence, content inventory, drafts, revisions and SEO metadata
- Run review queues, preflight checks and operation records
- Read Search Console diagnostics, plan growth work and internal links
- Deliver approved content to a selected CMS destination as a draft only
- Manage site-scoped access, MCP connections, integrations, brand voice and audit history
- When to use it
- Useful when an assistant should help produce and refine blog content across several sites while people keep control of review and publishing. Fits teams that want agent-authored drafts and CMS handoffs without giving the agent live publishing rights.
- Requirements
- A remote MCP endpoint at blogfactory.io over streamable HTTP, with OAuth authentication required. A BlogFactory workspace and site-scoped connection are needed; provider credentials stay outside the agent conversation. Self-hosting is possible with Node.js, PostgreSQL and S3-compatible storage.
Installation
In SourceWeft
- Open BlogFactory in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.blogfactory%2Fblogfactory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"blogfactory": {
"type": "http",
"url": "https://blogfactory.io/mcp"
}
}
}README
BlogFactory
The draft-only agent control plane for multi-site content operations.
Give agents useful authority through MCP. Keep people in control of review, approval, and CMS delivery.
Website · Self-host · MCP guide · Cloud billing · Release plan · AGPL-3.0-only
Self-hosted
Bring your own AI
Site-scoped access
Never publishes live
[BlogFactory turns source signals into reviewed CMS drafts while keeping live publishing locked]
A calmer content operation
BlogFactory keeps the operating context around AI-assisted content work in one place: source evidence, drafts, revisions, SEO metadata, review, preflight, delivery destination, and a sanitized operation record.
Agents do the work through MCP. The web app is where operators see what needs attention, resolve blockers, review the current version, and approve a CMS handoff. The server-enforced authority ceiling is intentionally narrow: no live publishing, deletes, credential access, arbitrary providers, or admin tools through MCP.
[BlogFactory brings sources, review, growth, and CMS draft delivery into one control plane]
Product captures
[BlogFactory Search Growth with complete-day provenance and next actions]
Search Growth turns evidence into reviewed action
Connect Search Console context, distinguish complete from preliminary data, rank work, plan it by date, and create a draft only when an operator is ready. Observation windows are shown as correlated signals, never as ranking guarantees.
[BlogFactory MCP Connections with site-scoped authorization]
MCP has useful authority and hard boundaries
Each connection is site-scoped. Clients discover the active catalog from the server, while provider credentials stay outside the agent conversation. The Review Card brings current revision context, warnings, destination selection, and explicit draft confirmation into compatible MCP clients.
Product captures from blogfactory.io. Values belong to the captured workspace; the tool catalog is discovered live.
What ships in v0.1.0
Self-host BlogFactory for free. BlogFactory Cloud is the managed service operated from the private BlogFactoryHQ/blogfactory-cloud repository; its pricing, subscriptions, checkout, and entitlement code is not part of this open-source core and never gates self-hosted instances. Read the release plan for the distribution roadmap.
Companion projects
Explore both projects in the Free & Open Source Tools hub.
Both projects work independently. They can supply or deliver content around BlogFactory, but they do not broaden BlogFactory's server-enforced draft-only authority.
Start locally
BlogFactory uses npm workspaces: a React/Vite web app and a Hono/TypeScript API, backed by PostgreSQL and S3-compatible storage.
The web app runs on http://localhost:8080 and the API on http://localhost:3000. Add only the credentials required for the flow you are testing; never point PostgreSQL integration tests at a shared production database.
Self-host with Docker
The verified topology includes the web app, API, PostgreSQL, MinIO, migrations, persistent volumes, and the bounded scheduler. Follow the full self-hosting guide before exposing an instance to the internet.
Hosted production
The managed service uses Cloudflare in front of an immutable Docker Compose deployment on Hetzner in Nuremberg. PostgreSQL 18, the Bun/Hono API, the persistent worker, the backup scheduler, and the web app run in that stack; private EU Cloudflare R2 stores images and age-encrypted database backups. GitHub Actions builds immutable images in GHCR; Vercel retains the last clean deployment as a DNS rollback target rather than serving current production traffic.
This hosted topology and the Cloud-only billing/authentication overlay are maintained in the private BlogFactoryHQ/blogfactory-cloud repository. Shared product changes originate in this public core and sync one way into Cloud; the hosted topology does not change the community self-host contract above.
How the system is shaped
Web and MCP are transports over the same services. Queue classification, revision rules, review preflight, Search Console reads, permissions, and CMS draft delivery are not duplicated in the UI or agent tools.
Documentation
- Architecture and service ownership
- MCP, OAuth, tool catalog, and Review Card
- Operations, deployment, and production acceptance
- Cloud billing, entitlements, and Managed AI
- Self-hosting with Docker Compose
- Release plan and Cloud boundaries
- Documentation index
- Contributing
Development checks
Database, tenancy, ledger, and shared control-plane changes also require npm run test:postgres against a disposable database.
BlogFactory is licensed under AGPL-3.0-only.
Source: README.md at commit ba763b4
Tools
0Version history
2- v0.5.1LatestNov 4, 2026
- v0.5.0Nov 4, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
