What is the key difference between Doc Manager and Bitatlas?

Doc Manager belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Bitatlas belongs to the Knowledge & Memory category with local stdio execution.

How do I install Doc Manager or Bitatlas 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 Doc Manager and Bitatlas free or paid?

Doc Manager operates under a Free / Open Source model (OAuth 2.0). Bitatlas operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Doc Manager lists 9 tools with 2 views and 1 GitHub stars. Bitatlas lists 6 tools with 3 views and 1 GitHub stars.

Can I use both Doc Manager and Bitatlas 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

Doc Manager vs Bitatlas

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

Doc Manager

Knowledge & Memory · Remote HTTP/SSE

Quality: 53/100 (Good) | Auth: OAuth 2.0

Bitatlas

Knowledge & Memory · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Verdict Summary: Choose Doc Manager if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Bitatlas 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 Doc Manager when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE 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.
Primary tools included: list_documents, get_document, search_documents.

Explore Doc Manager Details

Choose Bitatlas when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: .

Feature & Specification Comparison

Specification	Doc Manager giuliohome-org Knowledge & Memory	Bitatlas bitatlas-group Knowledge & Memory
Summary	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.	Zero-Knowledge Cloud Drive for Humans and Agents. Client-side AES-256-GCM encryption with 7 MCP tools for encrypted file vault management — upload, download, search, and organize files that the server never sees in plaintext.
Category & Scope

Tools & Capabilities Breakdown

Doc Manager Tools (9)

list_documents

List every doc with `id`, `title`, `encrypted` flag, attachment info, size

get_document

Fetch one plaintext document by id; refuses encrypted ones

search_documents

Case-insensitive substring search over titles (always) and plaintext content

get_attachment

Fetch the file attached to a doc (filename, bytes, base64, UTF-8 if applicable)

create_document

Create a new plaintext document; returns the new id

update_document

Replace content (and optionally title) of a plaintext document

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

Doc Manager Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "giuliohome-org-doc-manager": {
      "url": "https://claude.ai/api/mcp/auth_callback"
    }
  }
}

Bitatlas Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "bitatlas-group-bitatlas": {
      "command": "npx",
      "args": [
        "-y",
        "@bitatlas/mcp-server"
      ],
      "env": {
        "BITATLAS_API_KEY": "YOUR_BITATLAS_API_KEY_HERE",
        "BITATLAS_MASTER_KEY": "YOUR_BITATLAS_MASTER_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Doc Manager is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Bitatlas belongs to Knowledge & Memory using local stdio subprocess. Select Doc Manager when you need capabilities focused on knowledge & memory and Bitatlas when you require tools for knowledge & memory.

More alternatives to Doc Manager More alternatives to Bitatlas Knowledge & Memory category hub Canonical compare URL