Does Claude Code have persistent memory?

By default, Claude Code has no memory between sessions. Each new terminal session starts blank. Screenpipe gives Claude persistent memory by running a local MCP server Claude Code can query for your full work history: what you coded, read, discussed, and decided, captured continuously in the background.

How do you give Claude Code memory with Screenpipe?

Install Screenpipe, then add the Screenpipe MCP server to your Claude Code config (~/.claude.json). Once connected, Claude Code can query your local SQLite database for screen-captured context (recent terminal output, browser research, meetings, code edits) without you having to re-explain your work history.

What does the Screenpipe MCP server expose to Claude Code?

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

Is my code or screen data sent to Anthropic or any server?

No. Screenpipe captures everything locally and stores it in a SQLite database on your machine. The MCP server runs on localhost:3030. Nothing leaves your device unless you explicitly opt into cloud sync or a hosted AI model. See our security page for the full threat model and encryption details.

Does this work with Cursor, Cline, and other AI coding tools?

Yes. Any tool that supports MCP (Model Context Protocol) can connect to Screenpipe's local MCP server. Claude Desktop, Cursor, Cline, Continue, and custom agent setups all work the same way.

AI Agent Memory · MCP Integration

Claude Code Memory

Stop explaining your work to Claude every session. Screenpipe is a local-first, private AI agent memory. It captures everything you see, hear, and do, then feeds it to Claude Code via MCP so it always has full context.

Get started free Compare alternatives

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

How Claude Code 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 server runs on localhost

A local MCP server at localhost:3030 exposes search and activity tools. Add it to your Claude Code config in one line. Nothing goes to the cloud.

3. Claude queries your history

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

Quick setup

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

What Claude can remember with Screenpipe

Terminal & code context

Error messages, build output, test results, file diffs. Claude sees what you ran and what failed.

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 Claude.

Cross-session continuity

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

Give Claude Code memory today

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

Download Screenpipe

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

Frequently asked questions

Still have questions? Try Screenpipe free →