> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Screenpipe for developers: MCP and REST API for AI coding

> Give your AI coding assistant memory of your screen via MCP and the Screenpipe REST API — works with Claude Code, Cursor, Cline, Continue, and Gemini CLI.

Screenpipe gives developers a superpower: AI that knows what you've been working on. It captures your screen and audio 24/7 and makes it available to coding assistants via MCP and REST API.

<Tip>
  Want copy-paste API calls first? Start with [API recipes](/api-recipes). Building a recurring workflow? Use [scheduled task debugging](/task-troubleshooting).
</Tip>

## What developers use Screenpipe for

* **Code search across time** — find that code snippet you saw in a PR review last week, even if you closed the tab
* **Meeting recall** — search what was said in standups, design reviews, or pair programming sessions
* **Context for AI coding** — give Cursor, Claude Code, or Cline memory of what's on your screen right now and what you worked on earlier
* **Automated workflows** — scheduled tasks that auto-track time in Toggl, sync daily activity to Obsidian, or generate standup reports

## Integrations

Screenpipe works with any AI tool that supports MCP or HTTP APIs:

| Tool | Integration | Guide |
| - | - | - |
| **Claude Code** | MCP server — Claude Code can search your screen history, find code you saw earlier, recall meeting context | [Setup guide](/claude-code) |
| **Cursor** | MCP server — add Screenpipe as a context source for Cursor's AI | [Setup guide](/mcp-server) |
| **Cline** | MCP server — give Cline access to your full screen history | [Setup guide](/cline) |
| **Continue** | MCP server — add screen context to Continue's AI completions | [Setup guide](/continue) |
| **Gemini CLI** | MCP server — use Screenpipe with Google's Gemini CLI | [Setup guide](/gemini-cli) |
| **OpenCode** | MCP server — search screen history from OpenCode | [Setup guide](/opencode) |
| **Ollama** | Local AI — use any local model with Screenpipe, 100% private | [Setup guide](/ollama) |

## Quick start

1. [Download Screenpipe](https://screenpi.pe/onboarding)
2. Add the MCP server to your coding tool:

```json theme={"system"}
{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": ["-y", "screenpipe-mcp"]
    }
  }
}
```

3. Ask your AI assistant: "what was I working on in the last hour?" or "find the code snippet I saw in that PR review"

## Local API in one minute

```bash theme={"system"}
curl http://localhost:3030/health
curl "http://localhost:3030/search?q=error&content_type=all&limit=10"
curl "http://localhost:3030/activity-summary?start_time=2h+ago&end_time=now"
```

If API auth is enabled, add `-H "Authorization: Bearer $SCREENPIPE_API_KEY"`. See [API recipes](/api-recipes) for meetings, speakers, frames, memories, retention, and delete-range examples.

## Example prompts

Once Screenpipe is connected to your coding assistant:

* "Find the error message I saw in the terminal 30 minutes ago"
* "What did we discuss in the standup about the auth refactor?"
* "Show me the API endpoint I was looking at in the browser"
* "Summarize what I worked on today for my standup"

## Automate with scheduled tasks

[Scheduled tasks](/scheduled-tasks) are scheduled AI agents that run on your screen data. Developers use them for:

* **Time tracking** — auto-log coding time to Toggl based on active apps
* **Daily journals** — sync screen activity to Obsidian
* **Standup reports** — generate daily summaries of what you worked on

## Get Screenpipe

Screenpipe includes everything developers need — MCP server, scheduled tasks, cloud AI, and more.

[Download Screenpipe →](https://screenpi.pe/onboarding)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.