Does Windsurf have persistent memory between sessions?

By default, Windsurf has no memory between sessions. Each new session starts blank with no access to your previous work, decisions, or codebase history. screenpipe gives Windsurf persistent memory by running a local MCP server Windsurf 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 Windsurf via MCP?

Install screenpipe, then add the screenpipe MCP server entry to your Windsurf MCP config (~/.codeium/windsurf/mcp.json). Once connected, Windsurf 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.

What does the screenpipe MCP server expose to Windsurf?

The MCP server exposes search-content, keyword-search, and activity-summary tools. Windsurf 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?

screenpipe captures everything locally and stores it in a SQLite database on your machine. The screenpipe MCP server talks to the local screenpipe API at localhost:3030. In local-only mode, nothing leaves your device. Cloud AI models, sync, and team workflows are optional settings you configure separately.

Does this work with Cursor and Claude Code too?

Yes. Any tool that supports MCP can connect to screenpipe's local MCP server. Windsurf, Cursor, Claude Code, 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

Windsurf MCP Memory

screenpipe is a local-first, private AI agent memory. It captures everything you see, hear, and do, then exposes it to Windsurf via MCP so every session can access your recent work history. No re-explaining. In local-only mode, your history stays on your device.

Get started free Compare with other tools →

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

How windsurf mcp memory works

screenpipe runs a local MCP server that Windsurf queries for your work history. It captures screen and audio continuously, stores everything in SQLite on your device, and answers Windsurf's context queries in real time without any cloud dependency.

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 server connects to your local API

The screenpipe MCP server talks to the local screenpipe API at localhost:3030. Add it to your Windsurf MCP config in one step. In local-only mode, nothing leaves your device.

3. Windsurf queries your history

Windsurf can query the MCP server for recent terminal output, code context, meeting notes, or research. Ask about your history and it draws on your full local context.

Quick setup

Adding windsurf mcp memory with screenpipe takes under five minutes. Install screenpipe, add one config entry, and Windsurf can access your captured work history in the next session.

1
Install screenpipe
Download for macOS, Windows, or Linux at screenpipe.com/onboarding. Capture starts automatically.
2
Add screenpipe MCP to Windsurf config
In ~/.codeium/windsurf/mcp.json, add the screenpipe MCP server entry. Full instructions in the docs.
3
Windsurf has memory
Open a new Windsurf session. Ask it about your recent work and it will query your local screenpipe history for context.

What Windsurf can remember with screenpipe

Once connected via windsurf mcp, screenpipe surfaces any context Windsurf needs: what you built yesterday, which error blocked you, what you read and decided. Context persists across sessions because it lives in a local database, not in the model context window.

Terminal and code context

Error messages, build output, test results, file diffs. Windsurf 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 and conversation notes

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

Cross-session continuity

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

Give Windsurf persistent memory today

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

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

Download screenpipe

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

Using Cursor instead? Cursor MCP →

Frequently asked questions

Still have questions? Try screenpipe free →