Cursor - Mem0

Add persistent memory to Cursor with the Mem0 MCP server

Your AI assistant forgets everything between sessions. Mem0 fixes that by connecting Cursor to Mem0’s cloud memory layer via MCP so you can save and retrieve relevant context during coding sessions.

Prerequisites

Before setting up Mem0 with Cursor, ensure you have:

  1. A Mem0 Platform account and API key:
  2. Cursor installed (cursor.com)
  3. Your API key added to your shell profile (persists across sessions):
zsh

bash

echo 'export MEM0_API_KEY="m0-your-api-key"' >> ~/.zshrc
echo 'export MEM0_API_KEY="m0-your-api-key"' >> ~/.bashrc
source ~/.zshrc
source ~/.bashrc

Already have mem0 configured as an MCP server in Cursor? Remove the existing entry from your Cursor MCP settings before installing to avoid duplicate tools.

Installation

Option A: One-Click Deeplink (MCP Only)

The fastest way to get started. Click the link below to install the Mem0 MCP server directly in Cursor:Install Mem0 MCP in Cursor

Option B: npx (MCP Only)

npx mcp-add \
  --name mem0-mcp \
  --type http \
  --url "https://mcp.mem0.ai/mcp/" \
  --clients "cursor"

Option C: Manual Configuration (MCP Only)

Add the following to your .cursor/mcp.json:

{
  "mcpServers": {
    "mem0": {
      "url": "https://mcp.mem0.ai/mcp/",
      "headers": {
        "Authorization": "Token ${env:MEM0_API_KEY}"
      }
    }
  }
}

Start a new Cursor session and ask: "List my mem0 entities" or "Search my memories for hello". If the mem0 tools appear and respond, you’re all set.

Available MCP Tools

Once installed, the following tools are available in every Cursor session:

Tool Description
add_memory Save text or conversation history for a user/agent
search_memories Semantic search across memories with filters
get_memories List memories with filters and pagination
get_memory Retrieve a specific memory by ID
update_memory Overwrite a memory’s text by ID
delete_memory Delete a single memory by ID
delete_all_memories Bulk delete all memories in scope
delete_entities Delete a user/agent/app/run entity and its memories
list_entities List users/agents/apps/runs stored in Mem0

Example Workflow

# Session 1: Debugging a performance issue
You: The API endpoint /users is taking 3 seconds. Help me optimize it.

# Cursor agent searches memories, proceeds with investigation.
# Mem0 stores what you said as yours:
#   - Your preference: "Prefers query-level fixes over caching"
# ...and what the agent did as the assistant's:
#   - Learning: "N+1 query in UserService.getAll(): fixed with eager loading"
#   - Decision: "Added database index on users.email column"

# Session 2 (next week): Similar issue
You: The /orders endpoint is also slow, same pattern as before.

# Agent searches memories, retrieves the optimization learnings.
# Immediately checks for N+1 queries and missing indexes.

Troubleshooting