Connect an MCP client

Connection model

Your BlogFactory instance exposes a site-scoped Streamable HTTP endpoint at <instance-origin>/mcp. OAuth is the normal connection path when configured. A compatible client follows protected-resource metadata and receives only the sites and draft-only scopes the user approved.

A personal token is an advanced fallback. It is created in Control → MCP Connections, shown once, stored hashed, and belongs in the client environment—not a prompt, issue, or chat message.

Connect with OAuth

codex mcp add blogfactory --url https://content.example.com/mcp
codex mcp login blogfactory

Use a personal connection token

1. Open Control → MCP Connections on your instance and create a site-scoped token.
2. Save it when shown; it cannot be displayed again.
3. Store it as BLOGFACTORY_MCP_TOKEN in the client environment.
4. Add the MCP server with that environment variable.

codex mcp add blogfactory \
  --url https://content.example.com/mcp \
  --bearer-token-env-var BLOGFACTORY_MCP_TOKEN

Discover before you work

Run authenticated MCP initialization and tools/list instead of assuming a fixed client-side catalog. The current server catalog contains reading, generation, revision, Search Console, review, and CMS-draft tools; authority is always site-scoped and server-enforced.

401

Start the advertised OAuth flow or verify the local token environment variable

403

Request the approved site scope; do not bypass authorization

Conflict

Reread the post and send the current expected_updated_at value

Generation pending

Poll get_job; do not start a duplicate run