Integration Tutorial April 13, 2026

Give Cursor AI Persistent Memory

Cursor is the AI-first code editor that developers love -- but every new session starts from scratch. This guide adds the REM Labs MCP server to Cursor so your AI assistant remembers your project context, architecture decisions, and coding conventions across every session.

Why Cursor Needs Memory

Cursor's AI is powerful, but it forgets everything when you close a chat. That means you re-explain your stack, re-describe your conventions, and re-provide context every single session. With REM Labs MCP, Cursor's AI can store important information and recall it later -- automatically.

Step 1: Get Your API Key

npx @remlabs/memory

The free tier includes 1,000 memories and 60 requests per minute.

Step 2: Configure MCP in Cursor

Create or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "remlabs": {
      "command": "npx",
      "args": ["@remlabs/mcp-server"],
      "env": {
        "REMLABS_API_KEY": "your-api-key"
      }
    }
  }
}

For global configuration (all projects), add it to your Cursor settings under MCP Servers.

Step 3: Restart and Verify

Restart Cursor after saving. Open the Composer or Chat panel and type:

"What tools do you have available?"

Cursor should list remember, recall, and forget among its available MCP tools. If you do not see them, check that your API key is correct and that npx is available in your PATH.

Using Memory in Cursor

Once configured, interact naturally with Cursor's AI:

# Tell Cursor to remember something
"We use Prisma for the ORM with PostgreSQL. The schema
 is in packages/db/prisma/schema.prisma. Remember this."

# Later, in a new session
"What ORM do we use and where is the schema?"
→ Cursor recalls from REM Labs automatically

Cursor-Specific Tips

Use with Composer -- Cursor's Composer mode works with MCP tools, so you can store and recall memories mid-composition
Project namespaces -- set REMLABS_NAMESPACE in your env to isolate memories per project
Inline edits -- when Cursor makes inline edits, it can check memory for coding conventions first
@-mentions -- combine REM Labs memory with Cursor's @file and @codebase mentions for maximum context

Pro tip: Store your project's architecture overview as a memory on day one. Every future Cursor session will have instant access to your system design without eating context window tokens on file includes.

Global vs. Per-Project Config

Use per-project .cursor/mcp.json with different namespaces to keep memories isolated. Or use a global config with no namespace and let REM Labs' multi-signal search find the right memories across all your projects.

Give Cursor a memory that lasts

Free tier. One config file. Memory across every session.

Get started free →