What is the key difference between MCP Obsidian and Doc Manager?

MCP Obsidian belongs to the Knowledge & Memory category with local stdio execution, while Doc Manager belongs to the Knowledge & Memory category with local stdio execution.

How do I install MCP Obsidian or Doc Manager in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Obsidian and Doc Manager free or paid?

MCP Obsidian operates under a Free / Open Source model (No auth required). Doc Manager operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

MCP Obsidian lists 6 tools with 4 views and 1,655 GitHub stars. Doc Manager lists 9 tools with 2 views and 1 GitHub stars.

Can I use both MCP Obsidian and Doc Manager together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Obsidian vs Doc Manager

In-depth architectural comparison of the MCP Obsidian and Doc Manager 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.

At a Glance & Executive Verdict

MCP Obsidian

Knowledge & Memory · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

Doc Manager

Knowledge & Memory · Local stdio

Quality: 47/100 (Fair) | Auth: OAuth 2.0

Verdict Summary: Choose MCP Obsidian if you need specialized Knowledge & Memory tools running via a local process. Choose Doc Manager if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

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 Doc Manager when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: AZURE_STORAGE_ACCOUNT, AZURE_STORAGE_ACCESS_KEY, RUST_ROCKET_EXACT_ORIGIN, OAUTH_PROVIDER, OAUTH_PUBLIC_BASE_URL, OAUTH_ALLOWED_USERS, MCP_READ_ONLY.

Feature & Specification Comparison

Specification	MCP Obsidian bitbonsai Knowledge & Memory	Doc Manager giuliohome-org 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.	Personal document vault on Azure Blob Storage with a built-in MCP server. Client-side AES-256-GCM zero-knowledge encryption: encrypted docs stay opaque to Claude, plaintext docs are fully readable, writable, and searchable from chat.
Category & Scope

Tools & Capabilities Breakdown

MCP Obsidian Tools (6)

Local stdio MCP access to an Obsidian vault

Note reading, writing, patching, moving, and deletion

Multi-word search with BM25 reranking

Frontmatter and tag management

Vault statistics, directory listing, and batch reads

Read-only mode and vault-root path restrictions

Doc Manager Tools (9)

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).

MCP Obsidian Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "bitbonsai-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

Doc Manager Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "giuliohome-org-doc-manager": {
      "command": "npx",
      "args": [
        "-y",
        "giuliohome-org-doc-manager"
      ],
      "env": {
        "AZURE_STORAGE_ACCOUNT": "YOUR_AZURE_STORAGE_ACCOUNT_HERE",
        "AZURE_STORAGE_ACCESS_KEY": "YOUR_AZURE_STORAGE_ACCESS_KEY_HERE",
        "RUST_ROCKET_EXACT_ORIGIN": "YOUR_RUST_ROCKET_EXACT_ORIGIN_HERE",
        "OAUTH_PROVIDER": "YOUR_OAUTH_PROVIDER_HERE",
        "OAUTH_PUBLIC_BASE_URL": "YOUR_OAUTH_PUBLIC_BASE_URL_HERE",
        "OAUTH_ALLOWED_USERS": "YOUR_OAUTH_ALLOWED_USERS_HERE",
        "MCP_READ_ONLY": "YOUR_MCP_READ_ONLY_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Doc Manager belongs to Knowledge & Memory using local stdio subprocess. Select MCP Obsidian when you need capabilities focused on knowledge & memory and Doc Manager when you require tools for knowledge & memory.

More alternatives to MCP Obsidian More alternatives to Doc Manager Knowledge & Memory category hub