What is the key difference between Piia Engram and Codebase Memory MCP?

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

Piia Engram 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?

Piia Engram lists 58 tools with 1 views and 160 GitHub stars. Codebase Memory MCP lists 14 tools with 7 views and 42,895 GitHub stars.

Can I use both Piia Engram 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

Piia Engram vs Codebase Memory MCP

In-depth architectural comparison of the Piia Engram 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

Piia Engram

Knowledge & Memory · Local stdio

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

Codebase Memory MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Piia Engram 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 Piia Engram 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: get_user_context, wrap_up_session, memory_store.

Explore Piia Engram 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	Piia Engram Patdolitse Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Persistent user identity across AI tools. Stores preferences, lessons, and decisions as local JSON; 13 core MCP tools share them with Claude Code, Cursor, Codex, and any MCP client. Knowledge governance (staging→verified), AES-256-GCM encryption, cross-tool sync. pip install piia-engram	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

Piia Engram Tools (58)

get_user_context

Startup** — Load identity + knowledge at session start (supports `token_budget` for context size control)

wrap_up_session

Session end** — Save insights + sync at session end

memory_store

Writeback** — Unified write endpoint: routes to add_lesson / add_decision / add_playbook by `kind

add_lesson

Store a reusable lesson learned

add_decision

Record a key decision with reasoning

add_playbook

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

Piia Engram Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "patdolitse-piia-engram": {
      "command": "uvx",
      "args": [
        "piia-engram"
      ]
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Piia Engram 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 Piia Engram when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.

More alternatives to Piia Engram More alternatives to Codebase Memory MCP Knowledge & Memory category hub Canonical compare URL