Drop this into any MCP client.
{
"mcpServers": {
"bilinc": {
"command": "python",
"args": ["-m", "bilinc.cloud_mcp"],
"env": { "BILINC_API_KEY": "bil_live_..." }
}
}
}MCP server
An MCP memory server that keeps a trail.
Bilinc exposes 8 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.
Python >=3.10.
pip install -U bilinc bilinc login --api-key bil_live_... bilinc quicktest
Package bilinc 2.2.0, licensed BUSL-1.1. The public package is a cloud-only SDK, CLI, and MCP adapter.
Tools
Three tools, deliberately.
commit_mem
Write durable agent state.
Each write carries provenance — which run, tool, or operator produced it — so the record can be audited later.
recall
Retrieve prior context and decisions.
Use it before a risky edit so the agent acts on what was already decided rather than re-deriving it.
status
Check hosted Cloud health and account state.
Confirms the API key is valid and the hosted surface is reachable before an agent depends on it.
Clients
Documented configurations, and everything else.
These have a tested configuration page in the docs.
Any MCP-compatible client works over the standard stdio transport, whether or not it is listed here.
Bilinc connects the same way everywhere
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.