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

Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution, while Engram belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

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

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

Which MCP server has more tools and community activity?

Moxie Docs MCP lists 12 tools with 21 views and 2 GitHub stars. Engram lists 6 tools with 1 views and 11 GitHub stars.

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

Moxie Docs MCP vs Engram

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

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

Engram

Knowledge & Memory · Remote HTTP/SSE

Quality: 55/100 (Good) | Auth: API Key required

Verdict Summary: Choose Moxie Docs MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Engram if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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).
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Choose Engram when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ENGRAM_GIT_REPO, ENGRAM_PORT, ENGRAM_JWT_SECRET, ENGRAM_WRITE_TOKEN, ENGRAM_READ_TOKEN.
Primary tools included: Git-backed markdown storage with no database dependency, Authority-aware search excluding superseded or expired notes, Per-agent read and write tokens for access control.

Feature & Specification Comparison

Specification	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory	Engram rwnalds Knowledge & Memory
Summary	MCP & Agent Skills for Automated Documentation, and codebase conventions + context	Second brain your agents read and write, over a git-backed markdown vault. Authority-aware search ranks superseded and archived notes below live ones (from frontmatter, no vector DB), so agents quote the current doc, not the dead one. Per-agent read-only or write tokens, a git audit trail of every change with diffs, a knowledge-graph dashboard, and Obsidian compatibility.

Tools & Capabilities Breakdown

Moxie Docs MCP Tools (12)

moxie.get_ai_context

Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.

moxie.get_doc_impact

Given the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.

moxie.get_api_context

Given paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.

moxie.review_change

Self-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.

moxie.get_conventions

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

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Engram Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rwnalds-engram": {
      "url": "https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=1202294&amp;theme=light&amp;t=1784627191540"
    }
  }
}

Frequently Asked Questions

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

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