Hermes

Full steps: connect.md · Quickstart.

Hermes talks to ValorBrain as a MemoryProvider, not as a generic MCP client with a hard-coded list of tools.

Token

npx -y @valorbrain/cli@latest init --agent --agent-caller hermes --json

Use the mcp_token (vbm_…). With an account, create the token under Settings → MCP tokens.

Hosted Hermes

The installer writes the plugin config for you:

npx -y @valorbrain/connect@latest --token <vbm_…> --harness hermes
hermes memory setup        # pick valorbrain

Memory providers are activated through memory.provider, not plugins.enabled. Without a local engine, the provider covers the tools and the lifecycle hooks (bootstrap, per-turn context, end-of-session extraction), which run on the hosted engine.

MCP only, without the plugin: use the same path as any client — https://mcpbrain.valor.digital/mcp with Authorization: Bearer <vbm_…>, or npx -y @valorbrain/cli mcp over stdio.

On-premise (Enterprise)

On a machine that already has the engine, the plugin is shipped from the engine tree (src/hermes/ → ~/.hermes/plugins/valorbrain). The public harness repo carries a vendored copy: ./install.sh hermes copies the plugin to ~/.hermes/plugins/valorbrain without needing the engine tree.

Tools

The old marketing /docs page that promises a fixed number of tools for the native plugin is stale. The live catalog is the generated catalog; a new token gets the agent toolset. Guide: MCP tools.

Verify

Call memory_prepare. To keep the account beyond 30 days, the human runs npx -y @valorbrain/cli init --email <email>.