REM Labs · Cursor

Memory that persists across every Cursor session

Cursor ships with short-context recall inside one project. REM Labs exposes a native Model Context Protocol server — your Composer, Chat, and Inline Edit read from the same persistent memory across every repo, every laptop, and every branch.

Get API key Full docs

Free tier · No credit card · Native MCP · Works with Cursor 0.44+

Why Cursor + REM

Three things MCP + a persistent substrate change about your editor.

Continuity across sessions

Composer's memory resets with each chat. REM doesn't. Project conventions, past refactors, the reason you chose Bun — all available in every new window.

9 Dream Engine strategies

Overnight, REM summarizes your day's decisions, links related architecture notes, and surfaces contradictions. Tomorrow's Composer starts smarter than yesterday's.

Cross-tool portability

What you teach Cursor, Claude Code sees. What your Slack bot remembers, Composer recalls. One MCP endpoint, every client.

Install in 60 seconds

Cursor already speaks MCP. You just tell it where REM's MCP server lives.

The dedicated @remlabs/mcp-cursor launcher is in private beta. The raw MCP config below is production-ready today — all it needs is an HTTP-speaking MCP client, which Cursor 0.44+ ships. Request launcher access in Discord.

Get your API key

Open Cursor's MCP config

In Cursor: Settings → Features → Model Context Protocol → Edit mcp.json. Or open ~/.cursor/mcp.json directly.

{
  "mcpServers": {
    "rem-labs": {
      "url": "https://remlabs.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk-rem-YOUR_KEY_HERE",
        "X-REM-Namespace": "cursor-default"
      }
    }
  }
}

Restart Cursor

Command palette → Reload Window. Open Composer — you'll see rem-labs listed as an available MCP server, with recall and remember tools. Done.

Common patterns

Three shapes: per-project namespaces, teaching the editor preferences, and a stdio fallback for pinned Cursor builds.

1. One namespace per project

mcp.json

Add multiple entries so the editor keeps your client work, your side projects, and your dotfiles separated.

{
  "mcpServers": {
    "rem-slopshop": {
      "url": "https://remlabs.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk-rem-YOUR_KEY",
        "X-REM-Namespace": "slopshop-web"
      }
    },
    "rem-remlabs": {
      "url": "https://remlabs.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk-rem-YOUR_KEY",
        "X-REM-Namespace": "remlabs-api"
      }
    }
  }
}

2. Teach Composer your conventions

Composer

Just tell it. Composer auto-calls the remember tool — next window recalls automatically.

You: "Remember that this repo uses Bun (not Node), Biome (not Prettier),
      and Vitest (not Jest). Always suggest commands and imports matching those."

Composer: (calls rem-labs/remember with each fact)
          "Stored. I'll default to Bun/Biome/Vitest going forward."

# Next day, different window, same repo:
You: "Add a test for the auth helper."
Composer: (silently calls rem-labs/recall first)
          "Here's a Vitest spec that runs with `bun test` — matches your
           project's conventions."

3. stdio fallback for older Cursor builds

stdio

If your Cursor version only supports stdio MCP (not HTTP), launch a tiny local proxy. No daemon needed.

{
  "mcpServers": {
    "rem-labs": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch",
               "https://remlabs.ai/mcp"],
      "env": {
        "MCP_AUTH_HEADER": "Bearer sk-rem-YOUR_KEY",
        "X_REM_NAMESPACE": "cursor-default"
      }
    }
  }
}

# @modelcontextprotocol/server-fetch bridges stdio <-> HTTP MCP.
# We ship a dedicated `@remlabs/mcp-cursor` launcher in private beta
# with streaming and retry built in — see the note above.

What you get

Everything Cursor's session-local memory leaves on the table.

Cross-session memory

One namespace per project. Restart Cursor, swap laptops, switch branches — your editor still knows the architecture.

Semantic search under 180ms

Composer calls recall inline — latency stays under the budget for a tool-call round-trip. No UX regression.

Overnight consolidation

Dream Engine summarizes yesterday's commits, decisions, and refactors into a brief. Tomorrow's first Composer question starts from context, not cold.

Shared across all your agents

What Composer learns today is queryable from Claude Code, a LangChain ops agent, or a Zapier automation. Same MCP endpoint, every consumer.