BlogFactory

For AI agents and operators

Use BlogFactory as your content operations work layer.

Self-host BlogFactory, then connect to its authenticated, site-scoped MCP endpoint to inspect content, prepare drafts, review changes, and deliver approved work to a CMS as a draft.

Self-host and connect

Streamable HTTP · OAuth · Site-scoped · Draft-only

BlogFactory self-hosted MCP
Authenticated

Endpoint

Connect to your instance.

Use your self-hosted origin plus /mcp as the remote Streamable HTTP server. A compatible client follows protected-resource metadata and asks the user to approve one site.

https://<instance-origin>/mcp
codex mcp add blogfactory --url https://content.example.com/mcp
codex mcp login blogfactory

Advanced fallback: create a personal token inside BlogFactory and store it only in the client environment. Never ask a user to paste a token into a prompt.

First session

Identify the connection before doing work.

  1. 01whoami
  2. 02list_sites
  3. 03get_workspace_digest
  4. 04list_action_items

Discover the current catalog through authenticated MCP initialization and tools/list. Do not assume a fixed tool count.

Working sequences

Use the narrow workflow for the task.

Create caller-authored content

create_draftget_postreview_post

Use create_draft when the caller already supplied the Markdown. Read the saved post before revising it.

Generate with a connected provider

generate_draftget_jobreview_post

Generation is asynchronous. Poll get_job until the draft is ready, then review the exact result.

Revise without overwriting work

get_postupdate_draftreview_post

Pass the current expected_updated_at value to update_draft. On conflict, reread instead of forcing the write.

Deliver an approved CMS draft

review_postlist_publish_targetspush_to_cms_draft

Resolve blockers, obtain explicit approval, and select a destination before delivery. Repeating the same version and destination is idempotent.

Search growth

Read Search Console dashboard, insight, analytics, URL inspection, and sitemap evidence before proposing a reviewed content action. Do not infer automatic publishing or guaranteed results.

Hard boundaries

Keep authority narrow and reviewable.

  • Never live-publish or delete content.
  • Never administer accounts or perform arbitrary bulk mutation.
  • Never request, reveal, or return CMS, provider, or MCP credentials.
  • Keep every read and write inside the authenticated user's approved site scope.
  • Stop CMS delivery at a draft and preserve optimistic locking and idempotency.

Recovery

Stop, refresh, and preserve the boundary.

401
Start the OAuth flow advertised by the protected-resource metadata.
403
Ask for the required approved scope; do not attempt to bypass authorization.
conflict
Reread the post and retry only with the current version.
generation pending
Poll get_job; do not start a duplicate generation run.
preflight blocker
Reread review_post and resolve the blocker before delivery.

Self-host, then connect the agent to one approved site.

Follow the MCP guide, authorize the client on your instance, and let the current server catalog describe the available tools.

Read the self-hosted MCP guide