Andrea9293 MCP vs Screenpipe

A side-by-side look at the Andrea9293 MCP and Screenpipe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Andrea9293 MCP logoAndrea9293 MCPKnowledge & Memory · Local subprocess (stdio)Local-first document management and semantic search for AI coding agents67GreatAuth: no auth requiredScreenpipe logoScreenpipeKnowledge & Memory · Local subprocess (stdio)Local-first workflow memory for AI agents. screenpipe lets MCP clients search selected screen, audio, app, and meeting context and turn real work into cited notes, SOPs, workflow reports, and automation candidates.72GreatAuth: api key required

Verdict: choose Andrea9293 MCP for knowledge & memory work as a local process; choose Screenpipe for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Andrea9293 MCP logoChoose Andrea9293 MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like add_document, delete_document, search_documents.
Explore Andrea9293 MCP

Screenpipe logoChoose Screenpipe when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: SCREENPIPE_LOCAL_API_KEY.
  • You want tools like search-content, synced-devices, search-synced-content.
Explore Screenpipe

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAndrea9293 MCP logoAndrea9293 MCPScreenpipe logoScreenpipe
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal67/100 · Great72/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredAPI key required
PricingFreeFreemium
Required env varsNone listedSCREENPIPE_LOCAL_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars34422,002
Directory activity 4 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools1130

Tools & capabilities

Andrea9293 MCP tools 11

  • add_documentAdd a new document to the knowledge base
  • delete_documentDelete a document from the collection
  • search_documentsSearch for chunks within a specific document using semantic similarity. Always tell the user if result is truncated because of length. for example if you recive a message like this in the response: 'Tool response was too long and was truncated'
  • get_documentUse this tool only when user explicitly requests it. Retrieve a specific document by ID. Always tell the user if result is truncated because of length. for example if you recive a message like this in the response: 'Tool response was too long and was truncated'
  • list_documentsList all documents in the knowledge base
  • search_all_documentsSearch for relevant chunks across ALL documents in the knowledge base using semantic similarity (hybrid: full-text + vector). Useful for cross-document search when you don't know which document contains the answer.
  • get_context_windowReturns a window of parent content sections around a central parent_index. Use parent_index values from search results. Always tell the user if result is truncated because of length.
  • get_ui_urlGet the URL of the web UI. use this tool when user ask you to access the web interface, when the user ask you to upload a file or when the user ask you the uploads folder path. All these function are available in the web UI.
  • get_uploads_pathGet the absolute path to the uploads folder where you can manually place .txt and .md files
  • process_uploadsProcess all .txt and .md files in the uploads folder and create embeddings for them
  • list_uploads_filesList all files in the uploads folder with their details

Screenpipe tools 30

  • search-contentSearch screen text, audio transcriptions, input events, memories, and parsed app data. Returns timestamped results with app context. USE WHEN: you need the actual text/content of a moment — quotes, screen text, transcript lines, or compact parsed messages, emails, tasks, documents, and code review — or want to filter by speaker/window. DO NOT USE for: broad questions like 'what was I doing?' (use activity-summary, it pre-summarizes apps + windows + transcripts). Also DO NOT USE for: targeted UI controls (use search-elements). Start with limit=5, increase only if needed. Per-result text is auto-truncated to 1000 chars; pass max_content_length=0 to opt out, or a custom integer to override.
  • synced-devicesList this signed-in user's Screenpipe devices that have uploaded Data Sync records, including each device name and last sync time. USE WHEN: the user asks what devices are available, names another device, or asks a cross-device question and you need the exact device_name filter. This never accepts an account or bucket identifier; the local app forwards the signed-in user's identity.
  • search-synced-contentSearch Data Sync records from this signed-in user's devices. Results include device name, device ID, and timestamp for attribution. USE WHEN: the user asks about another/named device, asks across devices, or local search does not cover the requested machine. For the current machine only, use search-content. Start with a narrow time range and limit=10.
  • list-meetingsList detected meetings (Zoom, Teams, Meet, etc.) with id, duration, app, attendees, and note status. Pass `q` to substring-match title, attendee names/emails, and notes — `q` searches ALL meeting history, so when looking for a meeting with a person or on a topic ('when did I last talk to Noah?'), pass `q` and OMIT start_time. Only constrain the time range when the question itself is time-bound. Results are newest-first; without `q`, old meetings only surface via time range or offset pagination. Follow up with get-meeting (id from results) for the full note and transcript.
  • activity-summaryRich activity overview: authoritative active minutes, app/window time, edited document paths, key text, and audio transcriptions, with optional parsed task context when available. USE WHEN: any broad question about what the user did — 'what was I doing?', 'how long on X?', 'which apps?', 'recap my morning'. This is almost always the right first call for time-range questions — usually sufficient without follow-up searches. Use parsed/path evidence to identify tasks, but only active-minute fields for duration; frame and row counts are never time. DO NOT USE for: finding a specific keyword (use keyword-search) or a specific UI control (use search-elements).
  • search-elementsSearch UI elements (buttons, links, text fields) from the accessibility tree, filterable by role. USE WHEN: you want a specific UI control or page-structure question — 'find every Submit button I saw', 'list the links in that page'. DO NOT USE for: general text/content (use search-content) or fast keyword lookup (use keyword-search).
  • frame-contextGet full accessibility text, parsed tree nodes, and URLs for a specific frame ID. Use after search-content to get detailed context for a specific moment.
  • export-videoExport an MP4 of screen recordings for a time range, with synced microphone audio. Frames are placed at their real timestamps, so the clip's duration matches the wall-clock span you requested (not a sped-up timelapse). Returns the file path. Can take a few minutes for long ranges.
  • update-memoryCreate, update, or delete a persistent memory (facts, preferences, decisions the user wants to remember). To retrieve memories, use search-content with content_type='memory'. To create: provide content + tags. To update: provide id + fields to change. To delete: provide id + delete=true.
  • get-feedbackSearch local user ratings and written comments attached to AI-produced notifications, chats, memories, blocks, artifacts, and other targets. Use before generating related work so you preserve what earned up ratings and correct what earned down ratings.
  • send-notificationSend a notification to the screenpipe desktop UI. Use high priority only for time-sensitive failures or decisions needing human attention; routine findings and completed tasks should be normal or low.
  • health-checkCheck if screenpipe is running and healthy. Returns recording status, frame/audio stats, timestamps.
  • +18 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Andrea9293 MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-documentation-server": {
      "command": "npx",
      "args": [
        "-y",
        "@andrea9293/mcp-documentation-server"
      ]
    }
  }
}

Screenpipe

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "YOUR_SCREENPIPE_LOCAL_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Andrea9293 MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Screenpipe belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Andrea9293 MCP for knowledge & memory work and Screenpipe for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Andrea9293 MCP is listed as free. Auth: no auth required. Screenpipe is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-documentation-server and screenpipe as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Andrea9293 MCP has a quality signal of 67/100 (Great) with 4 views, 0 installs and 344 GitHub stars. Screenpipe has 72/100 (Great) with 3 views, 0 installs and 22,002 GitHub stars.