Skip to content
MemStrata MemStrata

Integration: Cursor

Coverage status

Section titled “Coverage status”
PathStatusNotes
MCP server✅ SupportedCursor’s native MCP support (Settings → Features → MCP)
Browser extension✅ SupportedCaptures Cursor’s web-based AI chat panels
Harness—Not needed when MCP is active

Confidence: High. Cursor shipped first-class MCP support in v0.43. Both paths are tested on every MemStrata release.

Important caveat: Cursor Composer’s native inline generation (the “Apply” flow) is a closed subsystem. MemStrata can read the prompt you send to Composer via MCP, but it cannot intercept the internal generation pipeline. This means the harness cannot compress the context Cursor sends internally for Composer — only the context you explicitly route through MCP.

Section titled “Setup: MCP path (recommended)”

1. Start the MemStrata MCP server

Terminal window
memstrata serve --port 8080

2. Register in Cursor

Open Cursor → Settings → Features → MCP Servers → Add Server:

{
  "name": "memstrata",
  "url": "http://localhost:8080/mcp",
  "enabled": true
}

Or edit ~/.cursor/mcp.json directly:

{
  "mcpServers": {
    "memstrata": {
      "url": "http://localhost:8080/mcp"
    }
  }
}

3. Use MemStrata context in prompts

In Cursor Chat, reference MemStrata with @memstrata:

@memstrata What does the AuthService.login() method do and which tests cover it?

MemStrata returns a compressed, graph-aware context slice. You’ll see the token count in the chat header.

4. Verify

@memstrata status

Expected output:

MemStrata v5.2.x | Project: ~/my-project | Indexed: 1,243 files | MCP: active

Setup: browser extension path

Section titled “Setup: browser extension path”

The browser extension captures Cursor’s web-based AI panels (when Cursor is accessed in-browser or when using cursor.sh’s hosted interface).

1. Install the MemStrata browser extension

Available for Chrome, Edge, and Firefox from the respective stores. Search “MemStrata” or install from the extensions page.

2. Configure the extension

Click the MemStrata extension icon → Settings → Add provider → Select “Cursor.”

The extension will detect Cursor’s chat DOM and begin capturing turns automatically.

3. Verify

In the MemStrata dashboard (open with memstrata dashboard), the Sessions tab should show Cursor sessions appearing within a few seconds of starting a conversation.

What’s captured

Section titled “What’s captured”
SignalCaptured?Notes
Cursor Chat (sidebar)✅ YesVia MCP — full context compression
Cursor Composer prompts✅ PartialPrompt captured; internal generation pipeline not interceptable
Cursor Composer “Apply”❌ Not capturedClosed subsystem; see caveat above
Edit suggestions (diff view)✅ YesFile save events tracked for 24h survival
@codebase queries✅ YesMCP intercepts the context fetch
Cursor’s native codebase index—MemStrata supplements; does not replace Cursor’s index

Troubleshooting

Section titled “Troubleshooting”

@memstrata not found in Cursor Chat
MCP server must be running before Cursor starts. Restart Cursor after running memstrata serve.

MCP server shows in settings but context is empty
Check that memstrata index has run on your project: memstrata status should show a non-zero file count.

Browser extension not capturing Cursor sessions
Cursor’s desktop app uses Electron; the browser extension only captures web-based panels. Use the MCP path for the desktop app.

Composer capture is partial
This is expected — see the caveat in Coverage status above. The MCP path gives full coverage for Chat; Composer’s internal pipeline is not accessible to third-party tools.

Section titled “Related”