Integrations

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.

MCP · Search Console · RSS · Models · CMS destinations

Connection topology
Illustrative product schematic

BlogFactory · Editorial control schematics

Every connection stays attached to a site.

Site-scoped hub

BlogFactory

Control plane
01AgentsMCP clients
02CMS draftsWordPress · Ghost · Wix · Framer
03ModelsOpenRouter · OpenAI · Google
04EvidenceSearch Console · RSS · batch
Connection boundary · Site 01

Why BlogFactory

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.

CMS connections

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
BlogFactory integrations workspace with a connected CMS and available destinations
Product capture · August 23, 2026. Values shown belong to the captured workspace.

How it works

A bounded connection path for every site.

01

Select a site

Start with the workspace that owns the context and destination.

02

Connect the stack

Add agent, search, source, model, and CMS access as needed.

03

Test before delivery

Verify the connection and select the destination explicitly.

Capabilities and boundaries

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

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.