What is the key difference between Codebase Memory MCP and Doc Manager?

Codebase Memory MCP 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 Codebase Memory MCP 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 Codebase Memory MCP and Doc Manager free or paid?

Codebase Memory MCP 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?

Codebase Memory MCP lists 14 tools with 7 views and 42,895 GitHub stars. Doc Manager lists 9 tools with 2 views and 1 GitHub stars.

Can I use both Codebase Memory MCP 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

Codebase Memory MCP vs Doc Manager

In-depth architectural comparison of the Codebase Memory MCP 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

Codebase Memory MCP

Knowledge & Memory · Local stdio

Quality: 72/100 (Great) | Auth: No auth required

Doc Manager

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Codebase Memory MCP 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 Codebase Memory 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: index_repository, list_projects, delete_project.

Explore Codebase Memory MCP 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.
Primary tools included: list_documents, get_document, search_documents.

Feature & Specification Comparison

Specification	Codebase Memory MCP DeusData Knowledge & Memory	Doc Manager giuliohome-org Knowledge & Memory
Summary	Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp	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

Codebase Memory MCP Tools (14)

index_repository

Index a repository into the graph. Auto-sync keeps it fresh after that.

list_projects

List all indexed projects with node/edge counts.

delete_project

Remove a project and all its graph data.

index_status

Check indexing status of a project.

search_graph

Structural, BM25, and semantic search. Page structural rows with `offset`/`limit` and ranked semantic rows independently with `semantic_offset`/`semantic_limit`.

trace_path

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

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

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

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

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