MCP

ValorBrain exposes a Model Context Protocol server. The connection steps have one source, connect.md; the Quickstart repeats them.

• Transport: Streamable HTTP
• Endpoint: https://mcpbrain.valor.digital/mcp
• Auth: Authorization: Bearer <vbm_…> or OAuth 2.1 (dynamic client registration)
• Protocol: 2025-11-25 (see the server card)

The token: vbm_ only

The MCP host accepts only vbm_… tokens. Two ways to get one:

• No account: npx -y @valorbrain/cli@latest init --agent --agent-caller <agent-name> --json returns mcp_token (vbm_…), mcp_url and api_key (vb_agent_…, REST only), and saves them in the CLI config.
• With an account: valorbrain.valor.digital/settings/mcp-tokens.

A REST key (vb_…, vb_agent_…) or ingest key (fk_…) as an MCP bearer gets 401:

{
  "error": "wrong_credential_type",
  "hint": "Authorization: Bearer vbm_…",
  "docs": "https://valorbrain.com.br/connect.md"
}

The body also carries a message saying the signup returns both credentials and where to create a vbm_ token.

HTTP

Claude Code

claude mcp add --transport http --scope user valorbrain https://mcpbrain.valor.digital/mcp --header "Authorization: Bearer <vbm_…>"

Codex

export VALORBRAIN_MCP_TOKEN=<vbm_…>
codex mcp add valorbrain --url https://mcpbrain.valor.digital/mcp --bearer-token-env-var VALORBRAIN_MCP_TOKEN

Gemini CLI — ~/.gemini/settings.json

{"mcpServers":{"valorbrain":{"httpUrl":"https://mcpbrain.valor.digital/mcp","headers":{"Authorization":"Bearer <vbm_…>"}}}}

Cursor — ~/.cursor/mcp.json

{"mcpServers":{"valorbrain":{"url":"https://mcpbrain.valor.digital/mcp","headers":{"Authorization":"Bearer <vbm_…>"}}}}

VS Code — .vscode/mcp.json

{"servers":{"valorbrain":{"type":"http","url":"https://mcpbrain.valor.digital/mcp","headers":{"Authorization":"Bearer <vbm_…>"}}}}

claude.ai / Claude Desktop — Settings → Connectors → Add custom connector → URL https://mcpbrain.valor.digital/mcp. Sign-in is OAuth; there is no token to paste.

OAuth 2.1

Clients with OAuth 2.1 DCR discover auth from:

https://mcpbrain.valor.digital/.well-known/oauth-authorization-server

POST /oauth/register (RFC 7591) on that host returns 201. You do not need to pre-register a client. The token OAuth issues is also a vbm_.

stdio

For clients that only speak stdio, use this as the server command:

npx -y @valorbrain/cli mcp

It is a stdio ↔ Streamable HTTP proxy to the same endpoint. It uses the token saved by init (or VALORBRAIN_MCP_TOKEN, or --token <vbm_…>). It is not a separate protocol. See CLI.

Full install (optional)

npx -y @valorbrain/connect@latest --token <vbm_…>

@valorbrain/connect is the installer: it detects the harnesses on the machine and writes, for each one, the MCP server entry, the rules and the hooks. It is not an MCP server; do not use it as a stdio client's command.

First calls

1. memory_prepare — step 3 verification: who you are in this workspace and the memory relevant to the task.
2. whoami — confirm tenant and user. Stop if either is wrong.
3. memory_retrieve while you work — then memory_used.

tools/list is the live schema; trust it, not a screenshot. The default agent toolset is the working set, not the full catalog. The catalog and the tool count live in the generated catalog; the guide is MCP tools.

What not to do

• Do not point REST at mcpbrain. /search there is not search.
• Do not send a vb_, vb_agent_ or fk_ key as an MCP bearer. MCP tokens start with vbm_.
• Do not use @valorbrain/connect as a stdio server. The stdio server is npx -y @valorbrain/cli mcp.
• Do not call the deprecated tool store. The canonical write is memory_store.