We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

screenpipe

MCP server by screenpipe

Search your local screen recordings, audio transcripts and computer activity captured by screenpipe.

Runs locally (Runs on your machine: its page has the install command)Runs with npxNeeds an API key

Install screenpipe

Runs on your machine. Your client starts it with this command:

npx -y screenpipe-mcp@latest

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

  • SCREENPIPE_LOCAL_API_KEY secret optional Local API key of the screenpipe app (get it with: screenpipe auth token). Recommended: without it the server looks for the key at startup…

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/screenpipe

About

Connects an AI assistant to screenpipe, an app that continuously captures your screen and audio. Through the MCP server you can ask about what you saw, did or heard on your computer, such as what happened in the last five minutes or a summary of today's conversations.

It runs locally over stdio as the npm package screenpipe-mcp and needs the screenpipe app or CLI running on the same machine. screenpipe recommends connecting Claude Desktop from the app's Settings → Connections, which uses the app's bundled runtime and adds your SCREENPIPE_LOCAL_API_KEY. A manual npx setup works too; without the key the server has to find it at startup, which can be slow or fail to connect.

screenpipe is source-available under a commercial license, with personal non-commercial use permitted. Captured history is stored locally by default; cloud AI, transcription, sync and integrations you turn on in the app can send that context off the device. The MCP server also sends sanitized crash reports to screenpipe unless you set SCREENPIPE_MCP_SENTRY_DISABLED=1.

What you can do

  • Search local screen recordings with natural language
  • Search audio transcripts from meetings and calls
  • Review recent computer activity and app usage
  • Summarize a day's conversations and work
  • Give coding agents context about what you are working on

Tools

Local servers list their tools once they’re running, so we can’t show them here. Look for the list in its documentation; your client shows them after you add it.

Example prompts

  • What did I see on my screen in the last 5 minutes?

  • Summarize my conversations from today.

  • Find the document I was reading in the browser this morning.

  • What did we discuss in my last meeting?

Set up

Every client starts screenpipe on your machine with the same command. Pick yours; the page remembers your choice.

Note from mcp.tc: screenpipe recommends installing the screenpipe desktop app and connecting Claude Desktop from its Settings → Connections. For a manual setup, set SCREENPIPE_LOCAL_API_KEY to the key printed by: screenpipe auth token. The full installation steps are in the screenpipe-mcp README (Docs link).

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio screenpipe --env "SCREENPIPE_LOCAL_API_KEY=<YOUR_SCREENPIPE_LOCAL_API_KEY>" -- npx -y screenpipe-mcp@latest
  1. Start Claude Code and type /mcp. screenpipe should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "<YOUR_SCREENPIPE_LOCAL_API_KEY>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "<YOUR_SCREENPIPE_LOCAL_API_KEY>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "screenpipe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "${input:screenpipe-local-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "screenpipe-local-api-key",
      "description": "SCREENPIPE_LOCAL_API_KEY",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "<YOUR_SCREENPIPE_LOCAL_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add screenpipe --env "SCREENPIPE_LOCAL_API_KEY=<YOUR_SCREENPIPE_LOCAL_API_KEY>" -- npx -y screenpipe-mcp@latest

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.screenpipe]
command = "npx"
args = ["-y", "screenpipe-mcp@latest"]
env = { SCREENPIPE_LOCAL_API_KEY = "<YOUR_SCREENPIPE_LOCAL_API_KEY>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "SCREENPIPE_LOCAL_API_KEY=<YOUR_SCREENPIPE_LOCAL_API_KEY>" screenpipe npx -- -y screenpipe-mcp@latest

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "<YOUR_SCREENPIPE_LOCAL_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

Embed

Show screenpipe in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![screenpipe on mcp.tc](https://mcp.tc/i/screenpipe/badge.svg)](https://mcp.tc/i/screenpipe)
HTML
<a href="https://mcp.tc/i/screenpipe"><img src="https://mcp.tc/i/screenpipe/badge.svg" alt="screenpipe on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/screenpipe.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/screenpipe" title="screenpipe on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/screenpipe.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the screenpipe card to your site.

Markdown
Add the mcp.tc card for screenpipe, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/screenpipe.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="screenpipe"><a href="https://mcp.tc/i/screenpipe">screenpipe on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![screenpipe on mcp.tc](https://mcp.tc/i/screenpipe/badge.svg)](https://mcp.tc/i/screenpipe)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow screenpipe and we’ll email you when something changes.

  1. , Automatic check

    New version 0.20.4 (was 0.20.3). Read from npm.

  2. , Automatic check

    New version 0.20.3 (was 0.20.2). Read from npm.

  3. , Automatic check

    Tracking started: version 0.20.2.

FAQ

Can I paste mcp.tc/i/screenpipe into my MCP client?

No. screenpipe runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y screenpipe-mcp@latest.

Does screenpipe need an API key?

Yes. It reads SCREENPIPE_LOCAL_API_KEY from its environment, and SCREENPIPE_LOCAL_API_KEY is a secret. Put the value in your client’s config on your own machine, never in a shared file.

Is screenpipe a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y screenpipe-mcp@latest, which needs Node.js.

What can screenpipe do?

You can search local screen recordings with natural language, search audio transcripts from meetings and calls and review recent computer activity and app usage.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to screenpipe?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read screenpipe’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with screenpipe. This page was built from screenpipe’s public metadata, last checked on 4 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.