Claude Code

Persist Claude Code decisions without bloating chat context.

Attach Bilinc through the Cloud MCP adapter, then recall before edits and capture outcomes after runs.

Install from PyPIReview trust posture
Install pathPyPI package
RuntimeHosted Cloud
InterfacePython + CLI + MCP
Releasev2.3.9
Setup
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
MCP config
{
  "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.

Prompt
Use Bilinc Cloud as the durable memory layer.
Recall prior repo decisions before edits.
Commit only durable outcomes. Never save secrets, API keys, or cookies.
Claude Code landing pageMCP tools