Skip to main content
Screenpipe acts as a memory layer for AI — it gives LLMs context about what you’ve been doing on your computer.

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

Screenpipe has a built-in MCP server that works with Claude Desktop, Cursor, and other MCP-compatible tools:
Or run npx -y screenpipe@latest agent setup <target> (claude-desktop, cursor, claude-code, codex, openclaw, hermes, windsurf) to install the Screenpipe skills and register the MCP server in one command.
See MCP server setup for details.

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

Get Screenpipe

Screenpipe gives your AI assistants memory of everything on your screen. Download Screenpipe →