MCP integration

Expose Bilinc Cloud to agent runtimes and operators.

Use the Cloud MCP adapter when you want Bilinc behind a tool boundary, and use the CLI when you need direct hosted operator workflows.

Install from PyPIReview trust posture
Install pathPyPI package
RuntimeHosted Bilinc Cloud
InterfacePython + CLI + MCP
AccessBILINC_API_KEY
Cloud MCP adapter

Wire the stdio transport.

{
  "mcpServers": {
    "bilinc": {
      "command": "python",
      "args": ["-m", "bilinc.cloud_mcp"],
      "env": { "BILINC_API_KEY": "bil_live_..." }
    }
  }
}
CLI

Keep operator controls simple.

export BILINC_API_KEY=bil_live_...
bilinc commit --key USER_PREF --value '{"theme":"dark"}'
bilinc recall --query "user preference"
bilinc status
Tool surface

The 2.0 adapter keeps the public surface cloud-only.

The public package no longer ships local StatePlane/storage internals. Agent runtimes use hosted commit, recall, and status through BILINC_API_KEY.