Claude Desktop and claude.ai

OpenMemory authenticates with a static header (Authorization: Bearer om_...). It does not use OAuth. There are two ways to connect Claude's apps.

#Option A: custom connector with a request header

Custom connectors can send static request headers, as a beta that is available to some organizations.

1. Create a space and copy its key (see Quickstart).
2. In Claude, open Customize > Connectors > Add custom connector. On Team and Enterprise plans, an Owner adds connectors for the organization.
3. Enter the URL https://mcp.openmemory.sh.
4. Set authentication to No sign-in, then add a Request header:
   • Header: authorization
   • Value: Bearer om_... (include the word Bearer and the space)
5. Save, then enable the connector in a chat and ask Claude to call get_context.

Header values cannot be edited later. To change the key, remove the connector and add it again. If you do not see a request-header option, your organization does not have the beta. Use option B.

#Option B: Claude Desktop with mcp-remote

mcp-remote runs locally and forwards to a remote MCP server with any headers you give it. It needs Node.js. Edit claude_desktop_config.json (Settings > Developer > Edit Config):

{
  "mcpServers": {
    "openmemory": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.openmemory.sh", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer om_..." }
    }
  }
}

Keep the key in env as shown. Some clients, including Claude Desktop on Windows, do not escape spaces inside args, so Authorization:${AUTH_HEADER} has no space and the value with the space lives in env.

Restart Claude Desktop, then ask Claude to call get_context.

#Related

• MCP tools
• Agent quickstart