Skip to main content
OpenClaw and Hermes can use Brein through the same remote MCP server as any other AI client:
The client chooses the model. Brein provides the workspace data and actions, including Companies, Personas, Prospectos, Campañas, Cerebro, and Investigador.

​
Use OAuth when it is available

Prefer the client’s normal OAuth flow. Select the Brein workspace you want the agent to use, review the requested permissions, and finish authorization in the browser.

​
Use an API key when the client requires headers

Create a scoped key in Settings → API Keys and keep it in the client’s secret or environment store. For OpenClaw, the connection has this shape:
For Hermes, add the server under mcp_servers:
The exact environment-variable expansion depends on the client. Never save the raw key in a shared repository.

​
Verify the connection

  1. List the workspaces the credential can access.
  2. Run a small read such as a market search or a bounded CRM query.
  3. Confirm that the result belongs to the intended workspace.
  4. Reconnect the client after a tool change if the client caches its tool list.
A 401 means the credential did not reach Brein. A 403 means the credential is valid but does not have access to the requested workspace or action.