Obsidian MCP Pro vs Vault Health MCP

In-depth architectural comparison of the Obsidian MCP Pro and Vault Health 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 Obsidian MCP Pro 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: MCP_PORT, MCP_VAULT_PATH, MCP_TRUSTED_ORIGINS, MCP_LOG_LEVEL.
• Primary tools included: search_notes, get_note, list_notes.

Explore Obsidian MCP Pro Details

V

Choose Vault Health 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).
• Primary tools included: configure_vault, check_vault_health, find_orphans.

Explore Vault Health MCP Details

Feature & Specification Comparison

Specification	Obsidian MCP Pro rps321321 Knowledge & Memory	V Vault Health MCP Knowledge & Memory
Summary	Feature-complete Obsidian vault MCP server with 23 tools and 3 resources. Full-text search, note CRUD, frontmatter queries, tag management, backlinks, graph traversal (BFS up to 5 hops), orphan/broken link detection, and canvas support. Auto-detects vault, path traversal protection, MIT licensed.	Obsidian vault structural health: broken links, orphans, missing frontmatter, safe auto-repair.
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": {
    "rps321321-obsidian-mcp-pro": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-mcp-pro"
      ],
      "env": {
        "MCP_PORT": "YOUR_MCP_PORT_HERE",
        "MCP_VAULT_PATH": "YOUR_MCP_VAULT_PATH_HERE",
        "MCP_TRUSTED_ORIGINS": "YOUR_MCP_TRUSTED_ORIGINS_HERE",
        "MCP_LOG_LEVEL": "YOUR_MCP_LOG_LEVEL_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "vault-health-mcp": {
      "command": "uvx",
      "args": [
        "vault-health-mcp",
        "--vault",
        "/path/to/vault"
      ]
    }
  }
}

Related MCP Server Comparisons