Does Cursor have persistent memory between sessions?

By default, Cursor has no memory between sessions. Each new session starts blank and has no access to your previous work, decisions, or codebase history. screenpipe gives Cursor persistent memory by running a local MCP server Cursor can query for your full work history: what you coded, read, discussed, and decided, captured continuously in the background.

How do you connect screenpipe to Cursor via MCP?

Install screenpipe, then add the screenpipe MCP server entry to your Cursor MCP config (~/.cursor/mcp.json). Once connected, Cursor can query your local SQLite database for screen-captured context — recent terminal output, browser research, meetings, code edits — without you having to re-explain anything.

Does screenpipe work with Windsurf MCP?

Yes. screenpipe works with any editor that supports MCP (Model Context Protocol). For Windsurf, add the screenpipe MCP server to ~/.codeium/windsurf/mcp.json. The same local MCP server at localhost:3030 serves both Cursor and Windsurf simultaneously.

What does the screenpipe MCP server expose to Cursor?

The MCP server exposes search-content, keyword-search, and activity-summary tools. Cursor can ask 'what was I working on this morning?' or 'what error did I see in the terminal last hour?' and get real answers from your actual work history stored locally.

Is my code or screen data sent to any server?

In local-only mode, screenpipe captures and stores your history in a SQLite database on your machine. The screenpipe MCP server talks to the local screenpipe API, so Cursor can use that context without a required cloud path. Optional cloud AI, sync, exports, connectors, and team workflows are separate settings you can review before enabling.

Does this work with Claude Code and other AI tools too?

Yes. Any tool that supports MCP can connect to screenpipe's local MCP server. Claude Code, Cursor, Windsurf, Cline, Continue, and custom agent setups all work simultaneously — one screenpipe instance, one MCP server, all your AI tools share the same context.

AI Agent Memory · MCP Integration

Cursor MCP Memory

Stop explaining your codebase to Cursor every session. screenpipe is a local-first, private AI agent memory. It captures everything you see, hear, and do, then feeds it to Cursor and Windsurf via MCP so they always have full context.

Get started free Also works with Claude Code →

19,000+ GitHub stars · 300,000+ installs · backed by Y Combinator

How Cursor MCP memory works

1. Capture runs in the background

screenpipe records your screen and audio 24/7, locally. OCR extracts text from every window — terminal output, docs, browser tabs, Slack, Zoom — and stores it in a local SQLite database.

2. MCP talks to your local API

The screenpipe MCP server talks to the local screenpipe API at localhost:3030 exposes search and activity tools. Add it to your Cursor or Windsurf MCP config in one step. Local-only mode does not require a cloud path.

3. Cursor queries your history

Cursor and Windsurf can query the MCP server for recent terminal output, code context, meeting notes, or research. Ask about your history and they draw on your full local context — no re-explaining needed.

Quick setup

1
Install screenpipe
Download for macOS, Windows, or Linux at screenpipe.com/onboarding. Capture starts automatically.
2
Add screenpipe MCP to Cursor config
Add screenpipe-mcp@latest as a stdio MCP server in ~/.cursor/mcp.json (Cursor) or ~/.codeium/windsurf/mcp.json (Windsurf). Full instructions in the docs.
3
Cursor and Windsurf have memory
Open a new Cursor or Windsurf session. Ask it about your recent work and it will query your local screenpipe history for context.

What Cursor can remember with screenpipe

Terminal & code context

Error messages, build output, test results, file diffs. Cursor sees what you ran and what failed, even from yesterday's session.

Browser research

Docs you read, Stack Overflow answers, GitHub issues, captured by OCR even if you closed the tab.

Meeting & conversation notes

Decisions made on Zoom, Slack messages, voice notes — all searchable and available to Cursor and Windsurf.

Cross-session continuity

Yesterday's debugging session, last week's architecture discussion. Context that survives closing the editor.

Give Cursor persistent memory today

Free to start. Local-first. Works on macOS, Windows, and Linux.

Download screenpipe

Also works with Claude Code, Cline, Claude Desktop, and any MCP-compatible agent. Security & privacy details →

Frequently asked questions

Still have questions? Try screenpipe free →