Integrations
Editors, harnesses and connectors that actually exist today: not the ones a README hoped for.
ValorBrain talks to any MCP client and any HTTP client. The pages below are the combinations we run ourselves or ship installers for.
Claude Code
MCP HTTP or stdio. Rules for consult-then-declare.
Cursor / Windsurf
OAuth DCR or a vbm_ token.
Grok
Harness templates + @valorbrain/connect.
Hermes
Native MemoryProvider plugin.
OpenClaw
memory slot plugin.
ZCode
Marketplace plugin with hooks and a skill.
Connectors
Notion, Drive, Slack, GitHub, Linear — BYOK, Starter+.
Hosted vs on-premise
Hosted (start here): no engine on your laptop. The harness talks to
mcpbrain with a vbm_ token, or to REST with a vb_agent_ key from the
CLI.
On-premise (Enterprise): the engine on your network is part of the
Enterprise plan — there is no community or self-service edition and no public
docker compose up; deployment is accompanied by our team.
What Enterprise includes.
The quality loop (every harness)
- Consult before answering — memory is authoritative about the operation; training data is not.
- Declare what you used —
memory_usedwith the docids you relied on. When the human confirms or corrects, passverdict.
If a README tells you to run valorbrain setup harness <name>, that
subcommand is not on the published CLI. Use the page for that harness
instead.