V4 · Integration

Cursor Integration.

Connect SuperLocalMemory to Cursor via MCP. Project decisions, code conventions, and debugging history persist across sessions in a local SQLite store — verify the integration contract in the installed Cursor release.

V4 AGPL v3 MCP stdio composerAgent

Quick Start

Install, connect, verify.

Package installation is separate from MCP configuration. Review the proposed Cursor MCP settings change before applying, then run a remember → recall round trip to confirm the integration.

Install SuperLocalMemory

Use pipx or uv with Python 3.11–3.14. Mode A does not require a model-provider key for its core path.

terminal

pipx install superlocalmemory
slm setup

Connect to Cursor

Run the connect command to review and apply the Cursor MCP configuration. Review the proposed settings change before confirming.

terminal

slm connect cursor

Or add manually in Cursor: go to Settings → Features → MCP Servers and add the server:

MCP configuration

{
  "mcpServers": {
    "superlocalmemory": {
      "command": "slm",
      "args": ["mcp"]
    }
  }
}

Verify the connection

Restart Cursor. In a Composer session, ask the agent to call get_status via the superlocalmemory MCP server. Then store a fact and recall it to confirm the round trip.

terminal — optional CLI check

slm status
# Expected: mode: A · provider: none · fact_count: 0
# Then try a round trip:
slm remember "Frontend uses Next.js App Router with server components"
slm recall "frontend architecture"

What You Get

Persistent context for Cursor.

Memory state persists across Cursor sessions in a local SQLite store. Each capability below reflects documented SLM behavior — verify the integration contract for the installed release.

01 · Decisions

Project-Wide Memory

Cursor can store and selectively recall project decisions, folder conventions, and architectural choices through configured SLM tools. Retrieval is not complete-project recall.

02 · Continuity

Cross-Tool Continuity

Documented clients can target the same configured SLM profile. Each client handoff still needs identity, scope, lifecycle, and restart verification.

03 · Privacy

Local Core Path

Core memory is SQLite-backed in the configured data root. Cursor, model providers, connectors, backups, proxies, and downloads retain separate network behavior and require separate assessment.

04 · Retrieval

Inspectable Recall

Local retrieval traces report candidate sources, fusion, reranker status, and measured latency. Performance depends on corpus, hardware, warmup state, and configuration.

05 · Portability

AGPL v3 Source

Full source code is public and auditable. Verify the installed release, optional dependencies, configured providers, connectors, and the Cursor client behavior.

06 · Patterns

Optional Learning

Optional behavioral signals can be surfaced as bounded context when configured. SLM does not by itself demonstrate that Cursor coding suggestions improve.

Common Questions

Questions about Cursor memory.

Install the package, run slm setup, and then run slm connect cursor to review the proposed MCP settings change before applying it. Then verify remember, recall, update, forget, reconnect, and uninstall behavior in your installed Cursor release.

Cursor versions with MCP support can be configured to call SLM tools. Verify tool discovery, identity, scope, remember, recall, mutation, restart, and removal against the exact Cursor release you are deploying.

Documented clients can target the same configured SLM profile. Protocol support or a named template alone is not proof of identity, scope, lifecycle, or handoff parity — run the integration contract in each client.

The core memory lookup runs against local profile state. End-to-end latency depends on corpus size, configuration, hardware, and any networked behavior in Cursor or optional providers; measure it in your deployment.

SuperLocalMemory is open source under the GNU Affero General Public License v3.0. The full source code is publicly available and auditable at GitHub.

Get started

Cursor sessions,
with durable project context.

Install, connect, then verify the memory round trip in Cursor before treating it as active.

Install V4.0 MCP Protocol