Introduction

ValorBrain is the company brain: shared operational memory for people and agents, with sources you can cite and facts you can correct.

ValorBrain is not a chatbot and not an agent orchestrator. It is the place your company keeps truth: decisions, incidents, people, keyed facts, and the context an agent needs before it answers.

Two products share one mental model:

  • Hosted — valorbrain.valor.digital (app) + valorbrain-api.valor.digital (REST) + mcpbrain.valor.digital (MCP).
  • On-prem (Enterprise) — the same engine running on your network, deployed and operated together with our team. It is not a self-service installer: see what Enterprise includes The architecture of what gets deployed is in the on-premise guide.

What you get

SurfaceWhat it is for
CLI @valorbrain/cliAgent signup, MCP stdio proxy, add, search. Zero npm dependencies. Node 18+.
MCPThe working set agents actually call: retrieve, prepare, store, used, curate.
RESTSame capabilities over HTTP for any language.
AppHumans: onboarding, tokens, connectors, billing.

Text is stored verbatim. A sentence written in Portuguese is retrieved in Portuguese. That is a product choice, not an accident.

Pick a path

You are…Start here
An AI agent with a shellQuickstart
A human setting up a workspacehttps://valorbrain.valor.digital then MCP
Wiring Claude Code / Cursor / GrokIntegrations
Calling HTTP from your own codeREST

Hosts (read this once)

HostRole
valorbrain-api.valor.digitalREST. Search, documents, agent signup.
mcpbrain.valor.digitalMCP only. Non-OAuth REST on this host returns 401.
valorbrain.valor.digitalSaaS app, ingest with fk_ keys, marketing, discovery.
docs.valorbrain.com.brThis site. (docs.valor.digital redirects here.)

Do not send /search or /documents to mcpbrain. The engine treats every non-OAuth path on that host as MCP transport.

For agents reading this page

The human usually sends: "Connect ValorBrain as your memory: read https://valorbrain.com.br/connect.md and follow it."

  1. If you have no account: run npx -y @valorbrain/cli@latest init --agent --agent-caller <agent-name> --json. Use the mcp_token (vbm_…) on MCP and the api_key (vb_agent_…) on REST only.
  2. Connect your MCP client with the command from the Quickstart and call memory_prepare.
  3. Prefer help --json over guessing subcommands. The published CLI does not have setup harness.
  4. After you retrieve, call memory_used with the docids you actually relied on.
  5. Full machine index: /llms.txt · complete dump: /llms-full.txt.

On this page