MCP Obsidian vs Weighted Compact

In-depth architectural comparison of the MCP Obsidian and Weighted Compact 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 MCP Obsidian 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: Local stdio MCP access to an Obsidian vault, Note reading, writing, patching, moving, and deletion, Multi-word search with BM25 reranking.

Explore MCP Obsidian Details

Choose Weighted Compact 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: Provably faithful recap with four invariants checked on all sessions, Local substrate of correction turns with multiple importance signals, Zero outbound network calls enforced by CI.

Feature & Specification Comparison

Specification	MCP Obsidian bitbonsai Knowledge & Memory	Weighted Compact zzallirog Knowledge & Memory
Summary	Universal AI bridge for Obsidian vaults using MCP. Provides safe read/write access to notes with 11 comprehensive methods for vault operations including search, batch operations, tag management, and frontmatter handling. Works with Claude, ChatGPT, and any MCP-compatible AI assistant.	Inspectable memory substrate for Claude Code. Three read-only MCP tools (searchpairs, compactsession, substrateinfo) over a local-first, signal-scored parse of /.claude/projects/. Per-pair scores are numpy columns on disk, not opaque vectors in a service. Zero outbound calls (CI-enforced).
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": {
    "bitbonsai-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

{
  "mcpServers": {
    "zzallirog-weighted-compact": {
      "command": "npx",
      "args": [
        "-y",
        "zzallirog-weighted-compact"
      ]
    }
  }
}

Related MCP Server Comparisons