Connect Claude.

Bring the same memory into Claude chats, Claude Desktop, and Cowork using a remote custom connector.

Browser sign-in · Web, Desktop & Cowork

Start in MarkdownMem

Sign in to the memory desk, select or create a memory store, and open Connect an agent. Copy the exact endpoint. The examples use placeholder workspace and store names.

Set up your client

1. In Claude Desktop, open Customize → Connectors → Add → Add Custom Connector.
2. Enter any title, such as MarkdownMem, and paste your MCP URL copied from the memory desk. Leave the other options blank, then choose Continue.
3. Connect and complete sign-in when your browser opens. Review the requested access before approving, then return to Claude.
4. Enable MarkdownMem for your conversation using the + menu → Connectors, then run the read check below. Ask to open the memory browser for the interactive editor.

These steps match Claude Desktop; labels may differ on web and Cowork. Team and Enterprise owners may need to add the connector before members can connect individually. Custom-connector allowances vary by plan. Remote connectors run through Anthropic's cloud, even in Claude Desktop; use your hosted URL, not localhost.

Check that it reads the right memory

Create /context.md in the browser with a harmless project fact. In your agent, ask:

Use MarkdownMem to read /context.md. Tell me the project fact it contains. Don't change any notes.

To check portability, connect a second client to the same store and ask it to read that note. To check writes, ask one client to save a small test note and confirm it appears in the web editor. Keep the client's usual tool approval controls enabled.

Tell the agent when to use memory

Before working, search MarkdownMem for relevant context. Read the matching notes. After finishing, update durable decisions and preferences. Don't save credentials or whole conversation transcripts.

Add this to your client's project instructions if you want it to apply in future sessions. Connecting an MCP server does not automatically import built-in memory or make every conversation save notes.

If something does not connect

• Copy the endpoint again: a different store path selects different memory.
• Complete the client’s sign-in action and check your account still has access to the store.
• For browser OAuth, remove any old Authorization header or expired key that would take precedence.
• For cloud or remote sessions, configure the connection in that environment; local settings may not carry over.
• If only the interactive editor is missing, check MCP Apps support. Text tools can work even when a host does not render the UI.

Browser OAuth acts with your account's current permissions. For a narrower, unattended connection, see store-scoped automation keys.

Current client references

Instructions reviewed September 6, 2026 against the sources below. These are configuration guides, not a claim that every client version, plan, or managed workspace has been certified.

• Claude custom connectors