What is the key difference between Montycat MCP — Shared AI Memory and Codebase Memory MCP?

Montycat MCP — Shared AI Memory belongs to the Knowledge & Memory category with local stdio execution, while Codebase Memory MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Montycat MCP — Shared AI Memory or Codebase Memory MCP 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 Montycat MCP — Shared AI Memory and Codebase Memory MCP free or paid?

Montycat MCP — Shared AI Memory operates under a Free / Open Source model (No auth required). Codebase Memory MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Montycat MCP — Shared AI Memory lists 0 tools with 0 views and 35 GitHub stars. Codebase Memory MCP lists 14 tools with 7 views and 42,895 GitHub stars.

Can I use both Montycat MCP — Shared AI Memory and Codebase Memory MCP 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

Montycat MCP — Shared AI Memory vs Codebase Memory MCP

In-depth architectural comparison of the Montycat MCP — Shared AI Memory and Codebase Memory 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.

At a Glance & Executive Verdict

Montycat MCP — Shared AI Memory

Knowledge & Memory · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Montycat MCP — Shared AI Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Codebase Memory MCP 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 Montycat MCP — Shared AI Memory 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).

Explore Montycat MCP — Shared AI Memory Details

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

Feature & Specification Comparison

Specification	M Montycat MCP — Shared AI Memory Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	One shared, persistent memory across AI agents and systems, with semantic recall and live updates.	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
Category & Scope

Tools & Capabilities Breakdown

Montycat MCP — Shared AI Memory Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

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

Montycat MCP — Shared AI Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "montycat-mcp-shared-ai-memory": {
      "command": "uvx",
      "args": [
        "montycat-mcp"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Montycat MCP — Shared AI Memory More alternatives to Codebase Memory MCP Knowledge & Memory category hub Canonical compare URL