One memory for your work in Claude.

Connect your conversations

For web and desktop use, connect a running Memrain server through a custom OAuth connector. Your operator registers the connection and provides its details privately. Use a Claude account that supports custom connectors, then verify the connection’s readable sources and write destination. The setup guide covers plan requirements and the current connection flow.

Bring memory into coding work

If you work in Claude Code, add the same Memrain endpoint through HTTP MCP. The coding setup supports a personal access token or a registered OAuth connection. User-level configuration makes memory available across projects. Retrieve earlier decisions alongside the current checkout, check historical context against today’s code and save new conclusions when authorized.

• Use a credential issued for the intended person
• Verify readable sources and the write destination
• Keep credentials outside project files and saved notes

Connect your team

A Claude organization can share one connector while each member receives an individual enrollment grant. The operator prepares sources and private, single-use codes; the organization owner configures the connector. A member’s grant can be replaced or revoked without reconnecting everyone. Follow the documented fail-closed setup and verify source boundaries before loading shared material. Source separation is pilot-grade application control; enrollment does not provide federated single sign-on or automatic provisioning.

Keep the right context between sessions

After setup, ask Claude to call Memrain’s identity tool and confirm its grant. Read-only credentials remain read-only, and optional daily caps limit priced model calls. Import older conversation exports or coding-session logs separately when you want that history in memory; connecting alone does not upload it. Optional session-end capture requires explicit configuration and checks for failed uploads.