Screenpipe MCP

80/100

Capped at 80: 1 of 3 real tool calls passed in our test; the tests add up to 93. Why scores are capped

Last tested 2026-11-18 UTC (Fresh: tested within 30 days) Working (tool call tested 2026-11-18 UTC) No key needed for the tools we called

Advisories: not yet checked

Security review: not tested

Test points add up to 93; the score is capped at 80 because not every real tool call passed. Not a quality or security rating. Why scores are capped

Test points before the cap (93/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License3/10

Tested npm screenpipe-mcp 0.20.4 (SEE LICENSE IN LICENSE.md; no source repo linked in package metadata). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 34 tools (34 annotated by the server: 22 read-only, 1 destructive). Real calls: 1 of 3 real function calls passed. The two data calls need the screenpipe backend on localhost:3030.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): partial. 1 of 3 real function calls passed. The two data calls need the screenpipe backend on localhost:3030. Evidence: local test run, Nov 18, 2026 UTC.

Transport (tested 2026-11-18 UTC): stdio

Token cost (estimate): approx. 6733 tokens, cl100k estimate (34 tools, measured 2026-11-18 UTC, version 0.20.4). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 15 read, 10 write (state-changing), 9 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • activity-summary — unclassified
  • add-tags — write (state-changing)
  • control-recording — unclassified
  • create-pipe — write (state-changing)
  • export-video — unclassified
  • frame-context — unclassified
  • get-feedback — read
  • get-frame-elements — read
  • get-meeting — read
  • get-workflow — read
  • health-check — unclassified
  • keyword-search — read
  • list-audio-devices — read
  • list-meetings — read
  • list-monitors — read
  • list-pipes — write (state-changing)
  • list-unnamed-speakers — read
  • list-workflows — read
  • merge-speakers — write (state-changing)
  • pipe-logs — unclassified
  • run-pipe — unclassified
  • screenpipe-skills — unclassified
  • search-chats — read
  • search-content — read
  • search-elements — read
  • search-speakers — read
  • search-synced-content — read
  • send-notification — write (state-changing)
  • start-meeting — write (state-changing)
  • stop-meeting — write (state-changing)
  • synced-devices — unclassified
  • update-meeting — write (state-changing)
  • update-memory — write (state-changing)
  • update-speaker — write (state-changing)

handshake and tools listed without a recorded key or OAuth

Score 80/100 · Tools 34 · Token cost approx. 6,733 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.20.4 · Package screenpipe-mcp

Summary: Screenpipe MCP completed an MCP handshake without credentials and exposed 34 tools.

Evidence summary

Handshake
pass
Tools listed
34
Context cost
approx. 6733 tokens, cl100k estimate (34 tools, measured 2026-11-18 UTC, version 0.20.4; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-18 UTC

Test results

TestResultPointsEvidence
installpass20npm install screenpipe-mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 0s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 34 tools listed in 7.7s.
maintenancepass25Latest release published 15 days before test.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepartial3License not machine-detected as OSI (SEE LICENSE IN LICENSE.md).

Local-model readiness

Token cost (estimate): approx. 6733 tokens, cl100k estimate for 34 tools · about 82% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-18 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 34 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

e8c3ae571dc3: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "screenpipe-mcp",
  "version": "0.20.4",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-18",
  "tools_count": 34,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install screenpipe-mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 0s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 34 tools listed in 7.7s."
    ],
    "maintenance": [
      "pass",
      25,
      "Latest release published 15 days before test."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "partial",
      3,
      "License not machine-detected as OSI (SEE LICENSE IN LICENSE.md)."
    ]
  },
  "testedAt": "2026-11-18T04:19:16.345Z"
}

Install

npx -y screenpipe-mcp

Pin the version we tested

npx -y --ignore-scripts screenpipe-mcp@0.20.4

tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "screenpipe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@0.20.4"
      ]
    }
  }
}

Tools listed

search-chats, list-workflows, get-workflow, screenpipe-skills, search-content, synced-devices, search-synced-content, list-meetings, activity-summary, search-elements, frame-context, export-video, update-memory, get-feedback, send-notification, health-check, list-audio-devices, list-monitors, add-tags, search-speakers, list-unnamed-speakers, update-speaker, merge-speakers, start-meeting, stop-meeting, get-meeting, update-meeting, keyword-search, get-frame-elements, control-recording, list-pipes, create-pipe, run-pipe, pipe-logs

Quick config

{
  "mcpServers": {
    "screenpipe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install screenpipe-mcp --ignore-scripts (Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (34 in our test).
{
  "mcpServers": {
    "screenpipe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best monitoring MCP servers

FAQ

Is Screenpipe MCP deprecated?

No. Screenpipe MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.

What replaces Screenpipe MCP?

Nothing; Screenpipe MCP is not deprecated as of 2026-11-18 UTC.

Does Screenpipe MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 34 tools.

Embed the badge

TestedMCP: 80/100, tested 2026-11-18 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue