How does screenpipe complement Cursor Memories?

Cursor can automatically create project-scoped memories from your chats. screenpipe complements those memories with searchable context from outside the current Cursor project: terminal output, browser research, meetings, and other apps. Cursor can query that local work history through MCP when it needs broader context.

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.

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?

screenpipe captures everything locally and stores it in a SQLite database on your machine. The screenpipe MCP server is editor-agnostic and connects to your local screenpipe instance. In local-only mode, captured data stays on the device. Optional cloud AI, sync, connectors, exports, and team workflows are separate deployment choices.

Does screenpipe cursor mcp also work with Windsurf?

Yes. The same screenpipe MCP server works with any editor that supports MCP. For Windsurf, add the entry to ~/.codeium/windsurf/mcp.json instead. One screenpipe instance serves Cursor, Windsurf, Claude Code, Cline, and any other MCP-compatible tool simultaneously.

Does cursor mcp work with Claude Code and other AI agents?

Yes. The screenpipe MCP server is editor-agnostic. Claude Code, Cursor, Windsurf, Cline, Continue, and custom agent setups all connect to the same local screenpipe instance. Your context is available to all your AI tools from a single source of truth.

AI Agent Memory · MCP Integration

Cursor MCP Memory

screenpipe is local-first AI agent memory. It captures what you've seen, said, and heard, then exposes it to Cursor via MCP so every session can access your recent work history. No re-explaining. In local-only mode, your context stays on your device. Cloud sync and AI are opt-in.

Get started free Compare with other tools

Source-available · local-first · backed by Y Combinator

How Cursor MCP Memory works

screenpipe runs a local MCP server that Cursor queries for your work history. It captures screen and audio continuously, stores everything in SQLite on your device, and answers Cursor's context queries in real time. In local-only mode, your context stays on your device. Cloud sync and AI are opt-in.

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 is editor-agnostic and connects to your local screenpipe instance, exposing search and activity tools. Add it to your Cursor MCP config in one step. In local-only mode, captured data stays on the device. Cloud sync and AI are optional.

3. Cursor queries your history

Cursor 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 without any manual re-explanation.

Quick setup

Adding Cursor MCP Memory with screenpipe takes under five minutes. Install screenpipe, add one config entry to ~/.cursor/mcp.json, and Cursor can access your captured work history in the next session.

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

What Cursor can remember with screenpipe

Once connected via cursor mcp, screenpipe surfaces any context Cursor 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 Cursor's context window.

Terminal and 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 and conversation notes

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

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.

Source-available · local-first · backed by Y Combinator

Download screenpipe

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

Using Windsurf instead? Windsurf MCP

Frequently asked questions

Still have questions? Try screenpipe free