Hebbian Vault vs Hive

In-depth architectural comparison of the Hebbian Vault and Hive 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?

H

Choose Hebbian Vault 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).
• Primary tools included: configure_vault, vault_search, vault_read.

Explore Hebbian Vault Details

Choose Hive 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).
• Primary tools included: vault_query, vault_search, vault_list.

Explore Hive Details

Feature & Specification Comparison

Specification	H Hebbian Vault Knowledge & Memory	Hive mlorentedev Knowledge & Memory
Summary	Usage-adaptive Obsidian vault search: Hebbian + PageRank + BM25 hybrid ranking.	On-demand Obsidian vault access via MCP. Adaptive context loading (67-82% token savings), full-text and ranked search, health checks, auto git commit, and worker delegation to cheaper models. 10 tools, works with any MCP client.
Category & Scope	Knowledge & Memory

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": {
    "hebbian-vault": {
      "command": "uvx",
      "args": [
        "hebbian-vault",
        "--vault",
        "/path/to/vault"
      ]
    }
  }
}

{
  "mcpServers": {
    "mlorentedev-hive": {
      "command": "uvx",
      "args": [
        "--upgrade"
      ]
    }
  }
}

Related MCP Server Comparisons