Connect
MCP server

An MCP memory server that keeps a trail.

Bilinc exposes 11 tools over the standard Model Context Protocol stdio transport. Any MCP-compatible client can connect with one API key — and every write it stores carries provenance and a rollback path.

Get an API key MCP setup Tool reference

Drop this into any MCP client.

JSON

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

Python >=3.10.

Terminal

pip install -U bilinc
bilinc login
bilinc quicktest

Package bilinc 2.6.0, licensed BUSL-1.1. The public package is a cloud-only SDK, CLI, and MCP adapter.

Documented configurations, and everything else.

Documented

These have a tested configuration page in the docs.

Also compatible

Any MCP-compatible client works over the standard stdio transport, whether or not it is listed here.

Claude Code Codex Cursor Hermes-Agent opencode

Bilinc connects the same way everywhere

Coding agents Claude Code Codex Cursor opencode Hermes-Agent

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

Eleven tools.

What the local adapter gives an agent, as the tool reference lists them.

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.