Rag Kb vs Screenpipe

In-depth architectural comparison of the Rag Kb and Screenpipe MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Rag Kb when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Rag Kb Details

Choose Screenpipe when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Screenpipe Details

Feature & Specification Comparison

Specification	Rag Kb fish827-08 Knowledge & Memory	Screenpipe Knowledge & Memory
Summary	Local-first agent memory & knowledge service with hybrid retrieval (BGE-M3 dense vectors + BM25 via jieba, fused with RRF), document & webpage ingestion, and optional RAG answering via local Ollama. Single process, embedded ChromaDB, REST + native MCP server; fully functional offline without any LLM. Apache-2.0.	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.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "fish827-08-rag-kb": {
      "command": "npx",
      "args": [
        "-y",
        "fish827-08-rag-kb"
      ]
    }
  }
}

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

Related MCP Server Comparisons