Expose Bilinc Cloud to agent runtimes and operators.

Wire the stdio transport.

pip install -U bilinc
bilinc login

# Claude Code: adds Bilinc for every project
eval "$(bilinc mcp install --client claude-code)"

# Claude Desktop: prints the config and where it goes
bilinc mcp install --client claude-desktop

# Any other MCP client: plain mcpServers JSON
bilinc mcp install

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

bilinc mcp install fills in the absolute path of the Python that has Bilinc, and the adapter reads the key saved by bilinc login, so the config carries no key. On a machine without a saved key, add BILINC_API_KEY to env.

Keep operator controls simple.

pip install -U bilinc
bilinc start
bilinc login
bilinc quicktest
bilinc mcp install --client claude-code

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 list --prefix user.
bilinc history USER_PREF
bilinc confirm USER_PREF --reason "still accurate"
bilinc export -o bilinc-memory.json
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.3.9 adapter exposes Cloud operations through a tool boundary.

The public package ships CloudClient, CLI, and the Cloud MCP adapter. Agent runtimes use the key saved by bilinc login, or BILINC_API_KEY where no key is saved, for hosted commit, recall, and status operations.