Connect
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 free MCP setup MCP tools

Set it up.

MCP config

{
  "mcpServers": {
    "bilinc": {
      "command": "python3",
      "args": ["-m", "bilinc.cloud_mcp"]
    }
  }
}

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.

Bilinc connects the same way everywhere

Coding agents Claude Code Codex Cursor opencode MCP server

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 guides Compare options Use cases

The tools it gets.

Hermes-Agent connects over the standard MCP stdio transport; the generic MCP setup applies unchanged.

The tools of the Bilinc MCP adapter
Tool	What it does
`commit_mem`	Writes durable memory with key, value, memory type, importance, and provenance metadata. Returns an entry version you can reuse for optimistic concurrency.
`recall`	Retrieves prior state with query, profile, and limit. Smart retrieval is the profile argument, not a separate tool.
`revise`	Deliberately replaces a memory you already have. Returns memory_not_found rather than creating, so a correction stays distinguishable from an accidental overwrite.
`forget`	Destructive. Removes a memory from active recall. A reason is required and is written to the audit trail; the deleted value is never returned.
`status`	Reports the authenticated workspace, plan, limits, supported capabilities, and recall profiles. Read-only and never billed.
`snapshot`	Creates or lists project checkpoints. Create is metered; list is free. Neither returns the checkpoint contents.
`diff`	Compares a checkpoint against another checkpoint or current state. Free, and values are redacted unless explicitly requested.
`history`	Read-only and free. Returns one memory’s recorded changes, newest first, with the value before and after each change. Values from before the memory was forgotten are never returned.
`list_memories`	Read-only and free. Returns a page of stored memories ordered by key, with prefix, type, and updated-time filters and a cursor for the next page.
`confirm`	Records that an existing memory is still accurate without resending its value. The value stays as stored, its last-updated time moves to now, and history shows a confirmation. One write operation.
`rollback`	Destructive in execute mode. Preview is free and returns a short-lived confirmation token; execute needs that token and permanently discards everything changed since the checkpoint.

The tool reference The remote connector for Claude

Set it up in your client.

Each page has the setup, prompts to try and the questions people ask.