Hosting

Local stdio process backed by a running Screenpipe desktop/API service; optional Streamable HTTP mode

Transport

stdio by default; optional Streamable HTTP

Endpoint

Local process; no hosted endpoint documented

Authentication

Local API key may be required when Screenpipe local API authentication is enabled; the package can attempt local key discovery. Enterprise team tools require an admin token and may require a configured enterprise API base URL.

Requirements

• Node.js 18 or later and npm/npx on PATH.
• Screenpipe desktop application/service must be running and reachable on localhost:3030.
• Accessibility permissions are needed for documented macOS computer-control behavior.

Setup steps

1. Install and start the Screenpipe desktop application, then confirm its local API responds at http://localhost:3030/health.
2. Add an stdio MCP server with command `npx` and args [`-y`, `screenpipe-mcp@latest`].
3. If local API authentication is enabled, obtain the key using the documented Screenpipe app/CLI flow (`screenpipe auth token`) and pass it as SCREENPIPE_LOCAL_API_KEY through the client's secure environment setting; do not save the secret in shared catalog data.
4. Restart/reconnect the MCP client and inspect tools/list. Stdio exposes more tools than HTTP; the documented HTTP mode currently exposes search_content only.
5. If tools do not connect, verify Screenpipe is running, check the local health endpoint, confirm Node.js 18+, and refresh the local API key.

The official package README documents tool groups and mode-dependent differences; tool availability can depend on package version, running Screenpipe engine, local settings, and optional enterprise credentials.

• search-content

  Search local screen, audio, accessibility, and parsed capture records with filtering and pagination.

  01
• export-video

  Export a screen-recording range to a video file.

  02
• activity-summary

  Summarize activity for a time range.

  03
• list-meetings

  List meetings detected in the local capture store.

  04
• search-elements

  Search structured accessibility-tree and OCR elements.

  05
• get-frame-elements

  Retrieve UI elements associated with a frame.

  06
• frame-context

  Retrieve accessibility and parsed context for a frame.

  07
• keyword-search

  Search OCR and audio text using keyword matching.

  08
• get-meeting

  Retrieve meeting details and optional transcript.

  09

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• The MCP accesses sensitive local screen and audio capture data; use only with an account and device whose data may be exposed to the assistant.
• HTTP transport has a smaller documented surface than stdio.
• Some enterprise tools require a separate enterprise admin token and are absent without it.
• No MCP initialize, tools/list, or representative tool call was performed for this catalog entry.

• Official publisher MCP README

  Documents the `screenpipe-mcp` package, stdio/HTTP setup, runtime and local service requirements, authentication, tool groups, feature differences, enterprise credential dependencies and troubleshooting.

• Official product website and brand asset

  Official Screenpipe website identifies the product; its linked 180x180 Apple touch icon was downloaded, decoded as PNG, and visually checked on light and dark contact sheets.

• official tool documentation

  Maintainer README documents transport-dependent tool availability plus optional enterprise and workflow features; stored nine names are incomplete.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.