Connect an agent to its memory.

Every store has an MCP endpoint. The endpoint selects the context; a credential proves who can use it.

Choose a memory store

Open the memory desk, select a store, and choose Connect an agent. Copy the endpoint shown for that store.

https://markdownmem.com/mcp/workspaces/{workspace}/agents/{store}

Create a connection key

In Connect an agent, name the client, choose read-only or read/write access, and select an expiry. Copy the new key into your client's private secret settings. It is shown once. A separate key for each client makes revocation and replacement straightforward.

Configure Streamable HTTP

Set the endpoint above and an Authorization: Bearer YOUR_MARKDOWNMEM_KEY header. A common client configuration looks like this:

{
  "mcpServers": {
    "markdownmem": {
      "url": "https://markdownmem.com/mcp/workspaces/WORKSPACE/agents/STORE",
      "headers": { "Authorization": "Bearer YOUR_MARKDOWNMEM_KEY" }
    }
  }
}

Exact configuration varies by client. Clients that only support interactive OAuth are not supported yet. Do not paste a browser session token as a workaround.

Keep the boundary clear

The key works only for its selected store and within your current permissions. Read/write includes deleting notes where permitted. It cannot manage your account or billing. Never commit a real key to a repository or paste it into a conversation.

Replace or revoke a connection

Keys expire after 90 days by default. Create a replacement, update your client, verify it can read a note, and revoke the old key. Signing out of the browser leaves agent connections running; revoke a key in the connection screen to end its access.

Use a simple memory instruction

Read relevant notes from this store before starting. Save durable context and decisions after finishing. Update existing notes instead of copying the whole conversation.

The full API schema is public at the developer reference. Memory data requires authentication.