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

Engram Mcp 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 Engram Mcp 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 Engram Mcp and Moxie Docs MCP free or paid?

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

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

Can I use both Engram Mcp 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 Engram Mcp 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 Engram Mcp and Moxie Docs MCP free to use, or do they require API keys?

Engram Mcp 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 Engram Mcp and Moxie Docs MCP at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both cartisien-engram-mcp 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, Engram Mcp has a Quality Score of 60 /100 ( Good ) with 2 views, 0 installs, and 1 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

Engram Mcp vs Moxie Docs MCP

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

Engram Mcp

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Engram Mcp 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 Engram 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).
You have access to required keys: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
Primary tools included: remember, recall, search.

Explore Engram Mcp 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: MOXIE_TOKEN.
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Feature & Specification Comparison

Specification	Engram Mcp Cartisien Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

Tools & Capabilities Breakdown

Engram Mcp Tools (11)

remember

Store a new memory with automatic entity extraction, theme detection, and relationship mapping.

recall

Retrieve relevant memories with entity, theme, and emotional context. Returns 360° relational intelligence around the query.

Raw hybrid search with pagination and filtering. Use for precise control over results.

context

Get 360° context around a specific entity, theme, or memory. Returns timeline, relationships, emotional arc, and key memories.

impact

Analyze how a new piece of information would affect existing memory structure. Detects conflicts, affected entities, and themes before storing.

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

Engram Mcp Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cartisien-engram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cartisien/engram-mcp"
      ],
      "env": {
        "ENGRAM_DB": "YOUR_ENGRAM_DB_HERE",
        "ENGRAM_EMBEDDING_URL": "YOUR_ENGRAM_EMBEDDING_URL_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

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

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