Connect your agent.
Keep your context.

Keep the same memory wherever you work. Start here, or pick your tool below for exact steps.

Most agents: a name, a URL, and browser sign-in

Most clients that support remote MCP and browser sign-in use the same setup:

Open the memory desk, select or create a store, and choose Connect an agent. Copy its MCP URL.
Add an MCP connection in your agent. Enter any name, such as MarkdownMem, and paste the URL.
Choose Connect or Continue. Your browser opens for sign-in; review access, approve, and return to your agent.

The URL selects your store. Browser sign-in connects your account, with its current memory permissions. No API key is needed. For an unattended job restricted to one store, use an automation key.

Which URL should I give my agent?

Your store has its own MCP URL. There is no shared connection URL for every account: create or select a store in the memory desk and copy its exact URL. Use that same URL in each agent that should work with that memory. The public website and this guide help you get started; they are not MCP endpoints.

One memory, more than one agent

Connect another client to the same store and authorize it with your account. Ask the first agent to save a decision; ask the second to read it. There is no need to export and reimport notes every time you switch tools.

Optional keys for automation

Browser sign-in is the normal setup. For a headless job or a client without OAuth, create a named connection key in Connect an agent. Select read-only or read/write access and an expiry. The key is restricted to that one store and your current permissions; it cannot manage your account or billing. Read/write includes deleting notes where permitted.

Use one key per client, store it in private secret settings, and send it as an Authorization: Bearer header. Never put a real key in a URL, repository, or conversation. Keys are shown once and expire after 90 days by default. Create a replacement, verify it works, then revoke the old one. Browser sign-out does not disconnect agents.

Make the connection useful

Read relevant MarkdownMem notes before starting. Save durable decisions after finishing. Update existing notes instead of copying the whole conversation.

Need a hand? Contact support@markdownmem.com. Send the client name and error text, with credentials removed.