{
"mcpServers": {
"bilinc": {
"command": "python3",
"args": ["-m", "bilinc.cloud_mcp"]
}
}
}These are the tools of the local adapter, python3 -m bilinc.cloud_mcp. The Claude connector at mcp.bilinc.space keeps its current tool set for now.
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.
What the hosted adapter deliberately does not expose.
Operator and debug tooling — health probes, benchmarks, the local engine’s bulk import and export tools, workspace replay — stays local-only, as do the epistemic read tools for claims, contradictions, and graph queries. The hosted surface is the core memory lifecycle, nothing more.
Never expose raw API keys to chat or public logs.