English Français العربية

BlogFactory

Official registry Search and web

Agent control plane for multi-site content ops: research, drafts, review, CMS draft delivery.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http blogfactory 'https://blogfactory.io/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "blogfactory": {
            "type": "http",
            "url": "https://blogfactory.io/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. BlogFactory
  2. A calmer content operation
  3. Product captures
  4. What ships in v0.1.0
  5. Companion projects
  6. Start locally
  7. Self-host with Docker
  8. Hosted production
  9. How the system is shaped
  10. Documentation
  11. Development checks

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 · Release plan · AGPL-3.0-only

Self-hosted Bring your own AI Site-scoped access Never publishes live

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.

source evidence
  → agent work or caller-authored draft
  → revision + SEO metadata
  → human review + preflight
  → selected CMS destination as a draft

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.

Product captures

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.

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

OperateGrowControlDeliver
Sources, content inventory, revisions, review queue, runs, and image workflowsSearch Console diagnostics, optimization, growth plans, indexing, and internal linksSite-scoped access, MCP connections, integrations, brand voice, settings, usage, and audit historyPreflight, explicit destination selection, optimistic locking, idempotent CMS draft delivery

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.

ProjectUse it when
Ghost Publisher MCPYou need a local, Ghost-specific MCP server for drafts, diagnostics, scheduling, and separately approved publishing. Overview and install
Source-Backed Blog WriterYou need a portable Agent Skill for researching, drafting, refreshing, or auditing evidence-backed articles. Overview and install

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.

git clone https://github.com/BlogFactoryHQ/blogfactory.git
cd blogfactory
npm install
cp .env.example .env
npm run db:migrate
npm run dev

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

git clone https://github.com/BlogFactoryHQ/blogfactory.git
cd blogfactory
cp .env.self-host.example .env
# Fill every required value and set ADMIN_EMAILS.
docker compose build --pull api web
docker compose up -d

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

operators ── <instance-origin> ─────┐
                                    ├─ shared tenant-scoped services ─ PostgreSQL + S3-compatible storage
agents ───── <instance-origin>/mcp ─┘                                   └─ CMS drafts / Search Console / configured AI providers

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.

SurfacePurpose
MarketingOpen-source product overview and Cloud launch updates
Authenticated appOperations, review, growth, settings, and audit
https://blogfactory.io/mcpStreamable HTTP agent work layer
/.well-known/oauth-protected-resourceMCP protected-resource discovery

Documentation

Development checks

npm run typecheck
npm run lint --workspace=web
npm run test --workspace=web
npm run test:server
npm run build
git diff --check

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.

Frequently asked questions

What is BlogFactory?

Agent control plane for multi-site content ops: research, drafts, review, CMS draft delivery.

How do I install BlogFactory?

It runs as a remote server. In Claude Code: claude mcp add --transport http blogfactory 'https://blogfactory.io/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does BlogFactory need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is BlogFactory open source?

Yes. Its code is on GitHub under the AGPL-3.0 license.

Who maintains BlogFactory?

It is published by BlogFactoryHQ. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.