Codex / ChatGPT
Streamable HTTP
Agent control plane
Connect Codex, ChatGPT, and other MCP-compatible clients to a site-scoped content work layer with useful authority and hard boundaries.
BlogFactory · Editorial control schematics
Streamable HTTP
Why BlogFactory
Use one hosted Streamable HTTP MCP endpoint.
OAuth and personal tokens carry explicit scopes for one site.
CMS and provider credentials never return through agent tools.
Authenticated calls write sanitized lifecycle events without prompts, bodies, tokens, or keys.
Connection proof
Operators can see the endpoint, connection state, selected site, and working sequence in the same control surface.

How it works
Create a connection for the workspace the agent may operate.
Allow content reads, draft writes, or approved CMS draft delivery—nothing broader.
Use the web control plane or MCP Review Card before destination handoff.
Capabilities and boundaries
The current catalog covers discovery, drafts, review, search evidence, and draft delivery.
Connections cannot cross the product’s highest-authority line.
FAQ
Yes. Content, sources, permissions, provider access, search properties, and destinations remain scoped to the authorized site.
No. Agent authority stops at approved CMS draft creation. Live publishing, deletion, credentials, and account administration stay outside MCP.
Yes. The public repository is available for self-hosting as a release candidate. BlogFactory Cloud is not available yet.
Inspect the public source, then follow the source-build Docker Compose guide for the open-source release candidate.