Remote MCP

Connect Claude to Bilinc with one URL.

The hosted MCP server works in Claude on the web, desktop, mobile, Cowork and Claude Code. You sign in to Bilinc once; there is no API key to copy.

Install pathPyPI package
RuntimeHosted Cloud
InterfacePython + CLI + MCP
Releasev2.3.1
Connect

Add Bilinc as a connector.

In Claude, open Settings → Connectors → Add custom connector, name it Bilinc and use this URL:

https://mcp.bilinc.space/mcp

In Claude Code:

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

Claude opens bilinc.space to sign you in. On the approval screen you choose the workspace and whether the connection is read-only or read and write.

Tools

What Claude can do, and when it asks you.

recall

Search memory; each result carries its source, last update and version.

read · runs without asking

list_snapshots

List saved checkpoints.

read · runs without asking

diff

Compare a checkpoint with the current state or another checkpoint.

read · runs without asking

status

Workspace, plan, credits and whether this connection can write.

read · runs without asking

remember

Store a new memory. Never overwrites an existing key.

write · runs without asking

create_snapshot

Save a checkpoint of the whole workspace.

write · runs without asking

preview_rollback

Show what a rollback would change and issue a confirmation token.

write access · changes nothing

revise

Replace a memory; the old value stays in history.

write · Claude asks first

forget

Remove a memory from recall, with a recorded reason.

write · Claude asks first

rollback

Restore a checkpoint using the preview token.

write · Claude asks first

A read-only connection only sees the four read tools. Anything that changes or deletes an existing memory is marked destructive, so Claude asks before running it.

Safety

Claude can't silently overwrite your memory.

remember only creates new keys. Changing an existing memory goes through revise, which can require the version you last read, so a change made elsewhere is never overwritten unseen. Every write records its source as the connected app (for example mcp:Claude), every change is versioned, and checkpoints can be compared and rolled back.

Data and access

What is sent, and how to disconnect.

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 one hour 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.

Troubleshooting

Common messages.

"This connection is read-only": reconnect Bilinc and choose read and write. "Reconnect Bilinc": the connection was disconnected or expired; remove and add the connector again. "Credits are used up": check your plan under Usage.

For developers

Standards the server follows.

Streamable HTTP (stateless, JSON responses). OAuth 2.1 with PKCE (S256) for public clients, registered through Client ID Metadata Documents or Dynamic Client Registration. Discovery at /.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 are bound to https://mcp.bilinc.space/mcp and are not accepted by the REST API, which keeps using API keys.