Why AI needs memory
LLMs are stateless — they don’t know what you were working on 5 minutes ago. Screenpipe bridges this by:- Capturing everything on your screen 24/7
- Extracting app text primarily via accessibility APIs, with OCR fallback for visual-only surfaces
- Making it searchable via REST API on
localhost:3030
Connect to AI
MCP (recommended)
Screenpipe has a built-in MCP server that works with Claude Desktop, Cursor, and other MCP-compatible tools:Scheduled tasks (scheduled agents)
Scheduled tasks are AI agents that run on a schedule and act on your screen data automatically — like syncing to Obsidian, tracking time in Toggl, or sending daily summaries. Spin one up from the CLI —npx -y screenpipe@latest pipe install <url-or-path> && npx -y screenpipe@latest pipe enable <name> (bunx / bun x work too) — or ask any connected agent to build one for you.
Direct API
Any tool that can make HTTP requests can query Screenpipe:The local API needs no auth by default. If you’ve enabled API auth in settings, add
-H "Authorization: Bearer <your-api-key>" to these requests.Use cases
Privacy-first
- All data stays on your device
- Use local LLMs (Ollama, LMStudio) for complete privacy
- Filter what gets captured in Settings → Privacy — ignore or include specific apps, windows, and URLs (privacy filters)
- No data sent to cloud unless you explicitly choose cloud providers
Next steps
- Build a second brain — let your agent watch your activity and remember your workflows in the background
- Set up MCP server — connect to Claude, Cursor
- Set up scheduled tasks — scheduled AI agents
- API reference — REST API search parameters and endpoints
- Join our Discord — get help from the community