What is the key difference between Claude Engram and Moxie Docs MCP?

Claude Engram belongs to the Knowledge & Memory category with local stdio execution, while Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Claude Engram or Moxie Docs 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 Claude Engram and Moxie Docs MCP free or paid?

Claude Engram operates under a Free / Open Source model (No auth required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Claude Engram lists 6 tools with 8 views and 16 GitHub stars. Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars.

Can I use both Claude Engram and Moxie Docs 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.

How do I install Claude Engram or Moxie Docs MCP in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Claude Engram and Moxie Docs MCP free to use, or do they require API keys?

Claude Engram is listed under a Free / Open Source model with No auth required . Moxie Docs MCP operates under a Freemium model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Claude Engram and Moxie Docs MCP at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both 20alexl-claude-engram and moxie-docs-mcp as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Claude Engram has a Quality Score of 56 /100 ( Good ) with 8 views, 0 installs, and 16 GitHub stars. Moxie Docs MCP holds a Quality Score of 82 /100 ( Excellent ) with 17 views, 25 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Claude Engram vs Moxie Docs MCP

In-depth architectural comparison of the Claude Engram and Moxie Docs 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

Claude Engram

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 82/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Claude Engram if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs 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 Claude 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).
You have access to required keys: CLAUDE_ENGRAM_MODEL, CLAUDE_ENGRAM_EMBED_MODEL, CLAUDE_ENGRAM_EMBED_DIM, CLAUDE_ENGRAM_DEVICE, CLAUDE_ENGRAM_GPU_BULK_MIN, CLAUDE_ENGRAM_LIVE_MINE.
Primary tools included: Automatic hooks tracking edits, errors, tests, and decisions, Error deja-vu with past fix injection on recurring failures, Per-project code index for import verification and blast radius analysis.

Explore Claude Engram Details

Choose Moxie Docs MCP when:

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

Feature & Specification Comparison

Specification	Claude Engram 20alexl Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Persistent memory and session intelligence for Claude Code. Auto-tracks mistakes, decisions, and context via hooks. Mines session history for patterns and cross-session search. Loop detection, pre-edit warnings, context compaction survival. Runs locally with Ollama.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

Tools & Capabilities Breakdown

Claude Engram Tools (6)

Automatic hooks tracking edits, errors, tests, and decisions

Error deja-vu with past fix injection on recurring failures

Per-project code index for import verification and blast radius analysis

Durable per-project ring checkpoints for context compaction survival

Background and live session mining with cross-session search

On-demand tools like memory, session_mine, work, context checkpoints

Moxie Docs MCP Tools (12)

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

Claude Engram Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "20alexl-claude-engram": {
      "command": "python",
      "args": [
        "venv",
        "venv"
      ],
      "env": {
        "CLAUDE_ENGRAM_MODEL": "YOUR_CLAUDE_ENGRAM_MODEL_HERE",
        "CLAUDE_ENGRAM_EMBED_MODEL": "YOUR_CLAUDE_ENGRAM_EMBED_MODEL_HERE",
        "CLAUDE_ENGRAM_EMBED_DIM": "YOUR_CLAUDE_ENGRAM_EMBED_DIM_HERE",
        "CLAUDE_ENGRAM_DEVICE": "YOUR_CLAUDE_ENGRAM_DEVICE_HERE",
        "CLAUDE_ENGRAM_GPU_BULK_MIN": "YOUR_CLAUDE_ENGRAM_GPU_BULK_MIN_HERE",
        "CLAUDE_ENGRAM_LIVE_MINE": "YOUR_CLAUDE_ENGRAM_LIVE_MINE_HERE"
      }
    }
  }
}

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ],
      "env": {
        "MOXIE_TOKEN": "YOUR_MOXIE_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Claude Engram More alternatives to Moxie Docs MCP Knowledge & Memory category hub