Connect CLS++ Memory to Cursor

Give Cursor persistent memory across sessions with the CLS++ Memory MCP server. Tools exposed: recall_memories, store_memory, who_am_i.

Quick install (remote, OAuth — preferred)

Create .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "cls-memory": {
      "url": "https://www.clsplusplus.com/mcp"
    }
  }
}

• Project-scoped: .cursor/mcp.json (committed for your team)
• Global: ~/.cursor/mcp.json (personal, all projects)

Then open Cursor Settings → MCP, find cls-memory, and click Connect to start the login.

OAuth login

The CLS++ endpoint uses OAuth 2.1 + PKCE with Dynamic Client Registration. Cursor handles the whole flow for you — clicking Connect opens your browser (callback cursor://anysphere.cursor-mcp/oauth/callback), you sign in once, and Cursor caches the token. There are no secrets to put in mcp.json, so the file is safe to commit.

Fallback: stdio via the clsplusplus package (API key)

If you prefer a local stdio server with an API key (get one at https://www.clsplusplus.com):

{
  "mcpServers": {
    "cls-memory": {
      "command": "uvx",
      "args": ["clsplusplus"],
      "env": {
        "CLS_API_KEY": "${env:CLS_API_KEY}",
        "CLS_API_URL": "https://www.clsplusplus.com"
      }
    }
  }
}

Set CLS_API_KEY in your shell so it is never hard-coded in the file.

Verify it works

In Cursor Settings → MCP, cls-memory should show a green dot with its three tools. In Agent chat, ask: "Use cls-memory to store that I prefer TypeScript, then recall my language preference." The agent should call store_memory and then return "TypeScript" via recall_memories.

See examples/integrations/cursor-mcp.json for the copy-paste config.