22:40

Give Claude a memory.

Add Bilinc to Claude once, with one address. What you tell Claude is there in every new chat, on claude.ai, on your phone and in Claude Code.

https://mcp.bilinc.space/mcp

This address is for Claude, not for your browser. Paste it into Claude as shown below; Claude handles the sign-in.

initializeClaude connectssign inOAuth 2.1, you choose the accesstools/list10 tools

Create an account Read the full guide

Set it up in three steps.

One connector, and one memory, for Claude on the web, on your desktop and on your phone.

Add the connector. In Claude, open Customize → Connectors → Add custom connector. Name it Bilinc and paste the URL above.
Sign in and choose access. Claude opens bilinc.space. Sign in or create an account, pick a workspace, and choose read-only or read and write.
Ask Claude. Turn Bilinc on in a chat and ask, for example: “Check Bilinc: what did we decide for the billing database?”

In Claude Code

Terminal

claude mcp add --transport http --scope user bilinc https://mcp.bilinc.space/mcp

Then run /mcp, pick bilinc and choose Authenticate.

One memory, every Claude

Claude Desktop: Add the connector once in Customize → Connectors.
claude.ai: The same connector works in the browser.
Claude mobile: Connectors you add on the web or desktop are available in the iOS and Android apps.
Claude Code: Add it from the terminal with one command.

Watch the setup video

What Claude can do, and when it asks you.

A read-only connection only sees the four read tools. Revising, forgetting and rolling back always ask you first.

The ten tools of the Bilinc connector
Tool	What it does	Access	When it runs
`recall`	Search memory; each result carries its source, last update and version, and a marker when it is past its review window.	Reads	Runs without asking
`list_snapshots`	List saved checkpoints.	Reads	Runs without asking
`diff`	Compare a checkpoint with the current state or another checkpoint.	Reads	Runs without asking
`status`	Workspace, plan, credits and whether this connection can write.	Reads	Runs without asking
`remember`	Store a new memory. Never overwrites an existing key.	Writes	Runs without asking
`create_snapshot`	Save a checkpoint of the whole workspace.	Writes	Runs without asking
`preview_rollback`	Show what a rollback would change and issue a confirmation token.	Needs write access	Changes nothing
`revise`	Replace a memory, or confirm it by sending the same value; the old value stays in history.	Writes	Claude asks you first
`forget`	Remove a memory from recall, with a recorded reason.	Writes	Claude asks you first
`rollback`	Restore a checkpoint using the preview token.	Writes	Claude asks you first

Claude can’t silently overwrite your memory.

You choose read-only or read and write when you connect.
Revising, forgetting and rolling back always ask you first in Claude.
Every change is versioned and can be compared with a checkpoint.
Disconnect any time under Connected apps in the dashboard.

What is sent to Bilinc

When Claude calls a tool, the tool's arguments (memory keys, values, queries, checkpoint ids) go to Bilinc Cloud over HTTPS and are stored in the workspace you chose, as described in the privacy policy. Nothing else from your conversation is sent.

Access tokens last seven days and refresh automatically; refresh tokens are single use. Disconnect any app at any time under Connected apps in the dashboard, which cuts it off immediately.

The standards it follows

Standards the Bilinc MCP server follows
Area	What the server uses
Transport	Streamable HTTP (stateless, JSON responses)
Sign-in	OAuth 2.1 with PKCE (S256) for public clients, registered through Client ID Metadata Documents or Dynamic Client Registration
Discovery	`/.well-known/oauth-protected-resource/mcp` on mcp.bilinc.space and `/.well-known/oauth-authorization-server` on bilinc.space
Scopes	`memory:read`, `memory:write`, `offline_access`
Tokens	Bound to https://mcp.bilinc.space/mcp; the REST API does not accept them and keeps using API keys

Cursor, Codex and other MCP clients.

They use the Bilinc package. 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.

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```

Add Bilinc to Cursor. In ~/.cursor/mcp.json, or .cursor/mcp.json for one project:

mcp.json

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

Tell your agent how to use it. Paste this into the agent’s instructions.

Instructions for your agent

Use Bilinc Cloud as the memory layer for this Cursor session.
Recall project context before changing code.
Commit durable decisions, verification results, and remaining risks at session close.
Never store API keys, cookies, tokens, or private environment values.

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```
Add Bilinc to Codex. Codex reads its MCP servers from ~/.codex/config.toml:
config.toml
```
[mcp_servers.bilinc]
command = "python3"
args = ["-m", "bilinc.cloud_mcp"]
```

Tell your agent how to use it. Paste this into the agent’s instructions.

Instructions for your agent

Use Bilinc Cloud as durable memory for this Codex task.
Recall before risky edits.
Commit final outcomes, verification commands, files changed, and caveats.
Never save secrets, cookies, tokens, private keys, or raw API keys.

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```
Add it for every project. If you’d rather not use the connector, this adds the local adapter instead:
Terminal
```
eval "$(bilinc mcp install --client claude-code)"
```

Tell your agent how to use it. Paste this into the agent’s instructions.

Instructions for your agent

Use Bilinc Cloud for durable project memory.
Before editing, recall prior architecture, billing, auth, and deployment decisions.
After the run, commit only reusable outcomes and verification notes.
Never store secrets or raw customer data.

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```
Print the config. This prints the block and the file Claude Desktop keeps it in:
Terminal
```
bilinc mcp install --client claude-desktop
```

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```
Print the server entry. bilinc mcp install prints it with your Python path; add it to opencode’s MCP settings. The command and its arguments are the same in every client:
mcpServers
```
{
  "mcpServers": {
    "bilinc": {
      "command": "python3",
      "args": ["-m", "bilinc.cloud_mcp"]
    }
  }
}
```

Tell your agent how to use it. Paste this into the agent’s instructions.

Instructions for your agent

Use Bilinc Cloud for durable project memory.
Before editing, recall prior architecture, auth, and deployment decisions for this repo.
After the run, commit reusable outcomes and verification notes only.
Never store secrets or raw customer data.

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```

Print the server entry. bilinc mcp install prints it with your Python path; add it to the agent’s MCP settings:

mcpServers

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

Tell your agent how to use it. Paste this into the agent’s instructions.

Instructions for your agent

Use Bilinc Cloud as the durable memory for this agent.
Recall prior decisions and constraints before acting on a long-running task.
Commit only reusable outcomes, verification notes, and decisions — not transcripts.
Never store secrets, credentials, or raw customer data.

Install the package and sign in. One package gives you the Python SDK, the bilinc command and the MCP adapter; bilinc login opens your browser and saves the key on this machine.
Terminal
```
pip install -U bilinc
bilinc login
```

Print the server entry. Any client that can start a stdio MCP server can use Bilinc:

Terminal

bilinc mcp install

mcpServers

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

A page for each client.

The setup for one client, with prompts to try, what it changes and the questions people ask.

Go further.

Every tool, its arguments and what it costs are in the docs.