For Hermes-Agent

Give Hermes-Agent memory that survives the session.

Bilinc exposes a standard Model Context Protocol server over stdio, so Hermes-Agent connects with the same configuration shape as any other MCP client. No adapter to write.

Start freeMCP setupMCP tools
MCP config
{
  "mcpServers": {
    "bilinc": {
      "command": "python",
      "args": ["-m", "bilinc.cloud_mcp"],
      "env": { "BILINC_API_KEY": "bil_live_..." }
    }
  }
}
Memory prompt
Use Bilinc Cloud as the durable memory for this agent.
Recall prior decisions and constraints before acting on a long-running task.
Commit only reusable outcomes, verification notes, and decisions — not transcripts.
Never store secrets, credentials, or raw customer data.
What you get

Three tools, one API key.

  • commit_mem — write durable state with verification and provenance.
  • recall — retrieve prior decisions and context before acting.
  • status — check hosted Cloud health and account state.

Hermes-Agent connects over the standard MCP stdio transport. There is no Hermes-specific docs page yet; the generic MCP setup applies unchanged.

Before you wire it up

Working out whether you need this?

The agent memory guides cover what agent memory is and where vector search stops. The comparisons place Bilinc against Mem0, Zep, Letta, and plain vector storage.

Agent memory guidesCompare optionsUse cases