Bilinc
Start free
  1. Docs
  2. Use Bilinc
  3. Remote MCP for Claude

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.

Add Bilinc as a connector.

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

Text
https://mcp.bilinc.space/mcp

In Claude Code:

Terminal
claude mcp add --transport http --scope user 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.

The same address works in ChatGPT and Codex.

In ChatGPT, open Plugins in the sidebar, then choose Add → Add custom MCP server. Name it Bilinc and use the same URL. ChatGPT opens bilinc.space to sign you in.

In Codex:

Terminal
codex mcp add bilinc --url https://mcp.bilinc.space/mcp
codex mcp login bilinc

Every app you connect shares the same workspace memory: what ChatGPT saves, Claude and Codex can recall. Each memory records which app wrote it.

What Claude can do, and when it asks you.

recall

Search memory; each result carries its source, last update and version, and a marker when it is past its review window.

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, or confirm it by sending the same value; 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

dream_start

Start tidying memory: the entries changed since the last dream, for Claude to review.

write · runs without asking

dream_apply

Merge duplicates, retire stale entries, keep or flag the rest; undo with dream_undo.

write · Claude asks first

dream_undo

Undo a dream's own changes in one step, for 7 days.

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. The dream tools are how you ask Claude to tidy its memory; see Dream pass.

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.

Old is not the same as wrong.

A memory can stay true long after it was written. Recall shows how long ago each entry was last written or confirmed, and marks an entry as possibly outdated once it is past its review window. Nothing is hidden or deleted: the entry is still returned, with the marker.

The default window is 90 days for facts, decisions, how-tos and places, and 1 day for working notes. Events are history, so they are never marked. The marker only reflects the time since the last write or confirmation; it does not detect whether a fact has changed.

To confirm a marked memory that is still correct, revise it with the same value. That records a confirmation, refreshes its date and keeps the previous state in history.

If you want Claude to check before relying on a marked memory, add a line like this to your own Claude instructions or CLAUDE.md. It is your instruction to Claude; Bilinc does not change how Claude behaves.

Text
When Bilinc marks a memory as possibly outdated, ask me whether it still holds before relying on it.

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

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.

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.