Workspace Qdrant MCP vs Engram MCP

In-depth architectural comparison of the Workspace Qdrant MCP and Engram MCP 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 Workspace Qdrant MCP 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).
• You have access to required keys: QDRANT_URL.
• Primary tools included: search, retrieve, rules.

Explore Workspace Qdrant MCP Details

Choose Engram MCP 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).
• You have access to required keys: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
• Primary tools included: remember, recall, search.

Feature & Specification Comparison

Specification	Workspace Qdrant MCP ChrisGVE Knowledge & Memory	Engram MCP Cartisien Knowledge & Memory
Summary	Project-scoped semantic workspace memory for AI coding assistants. Watches your project files, auto-indexes code and docs into Qdrant with tree-sitter semantic chunking, LSP integration, and hybrid search (dense + sparse + RRF). 6 MCP tools: store, search, retrieve, grep, list, rules. Alpha — testers and feedback welcome.	Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.
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": {
    "chrisgve-workspace-qdrant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrisgve-workspace-qdrant-mcp"
      ],
      "env": {
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "cartisien-engram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cartisien/engram-mcp"
      ],
      "env": {
        "ENGRAM_DB": "YOUR_ENGRAM_DB_HERE",
        "ENGRAM_EMBEDDING_URL": "YOUR_ENGRAM_EMBEDDING_URL_HERE"
      }
    }
  }
}

Related MCP Server Comparisons