OzBrain for Hermes Agent
Put Hermes on the same brain as Claude.
Updated
OzBrain connects to Hermes Agent as a remote MCP server with OAuth. Add https://ozbrain.co/api/mcp with auth: oauth, run hermes mcp login ozbrain, and Hermes can read and stage into the same brain Claude and Cursor use. Keep Hermes memory for local recall inside Hermes; use OzBrain when the knowledge must stay true across agents and people.
Hermes already runs across messaging surfaces with skills and scheduling. Connecting OzBrain does not replace that runtime. It puts shared structured articles underneath it.
Config once, login once, then read the index.
- 01
Add the server
In ~/.hermes/config.yaml under mcp_servers, add ozbrain with url https://ozbrain.co/api/mcp and auth: oauth. hermes mcp add works too; those two fields are the ones that matter.
- 02
Sign in
From a fresh terminal, run hermes mcp login ozbrain and approve in the browser. Do not rely on in-session config auto-reload for the first OAuth pass.
- 03
Work
Start Hermes the way you usually do. Ask it to read the OzBrain routing index. Optionally run hermes mcp configure ozbrain to keep only the tools you want.
What Hermes can do once connected
The connector exposes your brain as tools. Hermes decides when to use them, 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 scheduled job or channel reply starts from structure instead of a private digester.
Pull articles a task needs
Briefings, backups, and messaging work can read the project article and the decisions that still hold, then cite them.
Stage what it learns
Worth-keeping facts stage into the same brain Claude and Cursor write to, with provenance for who made the change.
Surface conflicts before they land
If a write contradicts what the brain holds, the write pauses and Hermes sees the conflict. It can record an exception; a different agent or you must approve a supersede.
Hermes memory and OzBrain can coexist
Hermes memory is strong for recall inside Hermes. OzBrain is for the knowledge every agent and every collaborator you grant access to must share. Leave Hermes memory on; connect OzBrain when the canon has to travel.
Keep Hermes. Connect the shared brain.
Hermes remains the runtime: channels, skills, schedules. OzBrain is the structured knowledge underneath, shared with Claude, Cursor, and the people you let in.
Create your brain, add the MCP URL with auth: oauth, run hermes mcp login ozbrain, then ask Hermes to read the routing index.
Questions people ask before connecting
Should I turn Hermes memory off?
No. Leave it on for local recall inside Hermes. Use OzBrain for structured knowledge that Claude, Cursor, OpenClaw, and collaborators need to share.
What about headless or remote hosts?
Hermes documents paste-back and SSH port-forward paths for OAuth when the browser is not on the same machine. Follow their MCP OAuth docs rather than inventing a second flow here.
Can Hermes write conflicts into my brain?
Writes stage first. If a write contradicts canon, promote pauses. The agent that staged it can resolve with exception; supersede needs a different agent or a human. Silent overwrite is not how OzBrain works.
What if these steps do not match my Hermes build?
Tell us. Setup here follows current Hermes MCP docs; if your build differs, we will correct this page from a real report.