Wire the stdio transport.
{
"mcpServers": {
"bilinc": {
"command": "python",
"args": ["-m", "bilinc.cloud_mcp"],
"env": { "BILINC_API_KEY": "bil_live_..." }
}
}
}Keep operator controls simple.
pip install -U bilinc
bilinc start
bilinc login --api-key bil_live_...
bilinc quicktest
bilinc commit --key USER_PREF --value '{"theme":"dark"}'
bilinc recall --query "user preference"
bilinc revise --key USER_PREF --value '{"theme":"light"}' --reason "user changed it"
bilinc snapshot create --label before-autonomous-run
bilinc snapshot list
bilinc diff --from-snapshot snap_...
bilinc forget --key USER_PREF --reason "superseded by profile service"
bilinc status
bilinc health
# Rollback is two stages. Execute needs the token from the preview and
# never prompts interactively, so it stays safe inside automation.
bilinc rollback preview --snapshot snap_... --reason "undo bad agent run"
bilinc rollback execute --snapshot snap_... --reason "undo bad agent run" \
--confirmation-token <token-from-preview>The 2.2.0 adapter exposes Cloud operations through a tool boundary.
The public package ships CloudClient, CLI, and the Cloud MCP adapter. Agent runtimes use BILINC_API_KEY for hosted commit, recall, and status operations.