OzBrain for OpenClaw

One brain behind every OpenClaw channel.

Updated

OzBrain connects to OpenClaw over MCP at https://ozbrain.co/api/mcp. After you approve once, OpenClaw can read your routing index, pull the articles a channel task needs, and stage what it learns so Claude, ChatGPT, and Cursor share the same facts. OpenClaw stays the multi-channel runtime; OzBrain holds the shared canon.

Telegram, Discord, Slack, WhatsApp, Signal, email, CLI: without a shared brain, each channel starts from whatever that session still holds. Grant the same brain to a collaborator and their agents read it too.

Create your brain

Add the server, approve once, prove the tools.

  1. 01

    Add the server

    In the Control UI: Settings, then MCP, then Add server. Name it ozbrain. Transport: Streamable HTTP. URL: https://ozbrain.co/api/mcp. Or CLI: openclaw mcp add ozbrain --url https://ozbrain.co/api/mcp --transport streamable-http

  2. 02

    Sign in

    Run openclaw mcp login ozbrain and complete the browser approve flow. Tokens stay with OpenClaw for later sessions.

  3. 03

    Prove it

    Run openclaw mcp doctor ozbrain --probe. Then ask OpenClaw to read your brain’s routing index.

What OpenClaw can do once connected

The connector exposes your brain as tools. OpenClaw decides when to use them under your tool policy, and every write is attributed in the article history.

Read the routing index

A compact listing of every article and what it covers, so a channel reply starts from structure instead of whatever the last chat still held.

Pull articles for a channel task

A Slack brief or Telegram follow-up can read the client article, the project decisions, and your voice rules without you re-pasting them.

Stage what it learns

Facts worth keeping get staged and routed mid-work, so Claude and Cursor see them later, not only the OpenClaw session that found them.

Surface conflicts before they land

If a write contradicts what the brain holds, the write pauses and the agent sees the conflict. It can record an exception; a different agent or you must approve a supersede.

Configured once on the Gateway

The server definition lives with OpenClaw, so channel bots and CLI sessions can share it, subject to each session’s tool policy. Saving a definition is not enough: run the probe before you trust it in production.

Keep OpenClaw. Connect the brain under it.

OpenClaw remains the runtime across your channels. OzBrain is the structured knowledge those channels share with every other agent you use.

Create your brain, add https://ozbrain.co/api/mcp, approve once, then ask OpenClaw to read the routing index.

Create your brain

Questions people ask before connecting

Does this replace OpenClaw memory?

No. OpenClaw keeps runtime memory for the agent. OzBrain holds structured, shared canon across OpenClaw, Claude, ChatGPT, Cursor, and anyone you grant the brain to.

Do I need a plugin?

Not on current OpenClaw with native MCP. Use Settings, MCP, or the openclaw mcp CLI. Older builds that needed a bridge plugin should upgrade first.

Will channel bots write to my brain?

Only if that session is allowed to use the OzBrain tools under your tool policy. Connecting the server does not bypass OpenClaw’s policy controls.

What if these steps do not match my OpenClaw build?

Tell us. Setup here follows current OpenClaw MCP docs; if your build differs, we will correct this page from a real report.

The brain behind every agent.