How to connect an AI client to BlogFactory over MCP

Create a token, add the server, let an agent work to review.

About 5 minutes · Illustrative UI

Animated walkthrough: Connect an AI client over MCP

BlogFactory · example product “Plantwise”Illustrative UI

Control · MCP Connections

Create token
Site: Plantwise
Token: ••••••••••••••••
Shown once. Copy it now.

Step 1 of 5

Create a site-scoped token

In Control → MCP Connections, create a token for one site. It is shown once and stored hashed.

Terminal · your machine

$ export BLOGFACTORY_MCP_TOKEN=<paste token>
Run ⏎

Set for this session. Nothing is sent anywhere.

Step 2 of 5

Keep it in the client environment

Store the token as BLOGFACTORY_MCP_TOKEN in the client environment. Never paste it into a prompt, an issue or a chat.

Terminal · your machine

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

Server “blogfactory” added.

Step 3 of 5

Add the MCP server

Add the endpoint to your client. This is the Codex form; other clients take the same URL and bearer token.

AI client · first session

Ask: what can you do here?
  • whoamisigned in
  • list_sitesPlantwise
  • get_workspace_digestread
  • list_action_itemsread

Step 4 of 5

Discover the tools

Start with whoami and list_sites, and read the live tool list instead of assuming one. Every call stays inside the site you approved.

AI client · playbook

Run playbook prompt
  • discover_topicsDone
  • research_keywordDone
  • generate_draftAsked first
  • review_postWaiting for you

Step 5 of 5

Let it work, then stop at review

Paste the playbook prompt. The agent researches, drafts, checks and fixes, asks before it spends your model budget, and stops at review.

Illustrative UI: a composite of the real screens with an invented example product. It is not a recording, and no real account or data is shown.

What you need

  • TokenA site-scoped tokenConnecting an AI client over MCP
  • KeyA Brave Search API keySERP briefs, term comparison with top results and rank tracking
  • KeyYour own OpenRouter keyDraft generation and the AI search visibility check
  • ConnectionA connected CMSDelivery of an approved draft to WordPress, Ghost, Wix or Framer
More: who sets each one, and what stops without it
You needWho sets itWithout it
A site-scoped tokenYou, in Control → MCP ConnectionsThe client gets a 401 and cannot call any tool. Where your instance has OAuth set up, the client signs in instead and is still limited to the site you approve.
A Brave Search API keyYou: save your own key in Article Settings. A key set by the server operator is only a fallbackResearch returns the question tree only, and the rank tracker cannot run checks. Brave has a free tier, and searches bill to your own Brave account.
Your own OpenRouter keyYou, in the site settingsNo draft is generated and the AI visibility check does not run. Everything else on the plan sheet still works.
A connected CMSYou, in Control → IntegrationsNothing is sent. The draft stays in BlogFactory and the review steps still work.

Drafts only. BlogFactory only creates CMS drafts. It never publishes live on its own.

What it will not do

Boundary · BlogFactory only creates CMS drafts. It never publishes live on its own.
  • Live-publish, delete content, bulk-mutate or administer accounts.
  • Return a CMS, model or MCP credential to the client.
  • Reach another site. Authority is scoped to the approved site and enforced on the server.

Try the steps on your own site.

Every step above is in both editions. You approve each draft, and nothing publishes itself.