Tested integrations
Which clients we have actually tested.
Shared Brain speaks MCP over streamable HTTP. Any MCP host can connect, but “can connect” is not the same as “has been tested”, so this page keeps the two apart and states the date, the transport and the operations behind every claim.
Tested
Both entries below completed a describe → remember → recall round trip on the recorded date, over stdio. The remote HTTP/OAuth route is covered separately by the SDK harness and a live identity-provider run; a host is added here only after its transport and tool tests pass.
| Client | Last tested | Transport | Account requirements | Operations exercised | Setup | Limitations |
|---|---|---|---|---|---|---|
| Claude Code 2.1.285 (Anthropic) | 30 Sept 2026 | stdio | An MCP host configured with the workspace endpoint and an approved grant; sign-in through the workspace’s identity provider. | describe, remember, recall |
Guide | Only the stdio round trip is recorded. Remote HTTP/OAuth has not been verified for this host. |
| pi 0.99.1 (Earendil Works) | 30 Sept 2026 | stdio | An MCP host configured with the workspace endpoint and an approved grant. | describe, remember, recall |
Guide | Only the stdio round trip is recorded. Remote HTTP/OAuth has not been verified for this host. |
Candidates — not yet tested
These clients appear in setup examples and are reasonable candidates. They do not carry a supported badge, and we do not claim they work end to end until they pass the same tests.
- Claude web — connector OAuth registration is enabled; an end-to-end round trip is not yet verified.
- Cursor — MCP over streamable HTTP; setup example published.
- ChatGPT — custom connector (remote MCP server); setup example published.
- VS Code-based clients — MCP over streamable HTTP; setup example published.
- Hermes — candidate; no setup example published yet.
- OpenClaw — candidate; no setup example published yet.
What an integration does — and does not — do
- Saves only what the agent calls. Connecting does not import conversations. A record exists only after an agent calls
remember(or a person contributes one), and you choose whether writes land directly or wait for review. - Reads only the approved workspace. The endpoint path selects a workspace; the grant and its permissions decide what the caller may read. An unauthorised caller gets no content.
- Returns the current revision. A retrieval returns the current, authorised record with its source and revision. A superseded revision stays visible as history but is not returned as current.
- Needs the client to ask again. MCP tools are model-controlled: exposing memory tools does not mean an agent will use them at the right moment. A fresh session should recall at the start of a task.
- Notifies clients that subscribe. A client that keeps a cache should follow the change feed and discard it on
resync_required. A correction does not reach into a model’s context on its own.
How a host becomes “tested”. It must complete the transport handshake, the OAuth and grant-approval flow, and a describe → remember → recall round trip against a real workspace. The date, transport and operations are recorded, and the claim is withdrawn if a later run fails.
Ready to try it? Connect your agent, or read the public agent start guide.