Codebase Memory MCP vs Metis

In-depth architectural comparison of the Codebase Memory MCP and Metis 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 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 Metis 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: Project-aware memory with domain-specific knowledge layer, Cited answers sourced only from user’s indexed documents, Linked notes, meetings, ideas, and research materials.

Explore Metis Details

Feature & Specification Comparison

Specification	Codebase Memory MCP DeusData Knowledge & Memory	Metis SVerITG 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	A private, local research "second brain" for Claude: project-aware memory, cited answers from your own library (won't invent what it can't find), linked notes/meetings/ideas via a domain-specific knowledge layer, daily briefs (news + new papers in your field), a live meeting assistant, cross-pollination across your work, and 34 routed agents. A governed layer between you and the AI, with guardrails like data protection. A Research Cortex.

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": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "sveritg-metis": {
      "command": "npx",
      "args": [
        "-y",
        "sveritg-metis"
      ]
    }
  }
}

Related MCP Server Comparisons