What is the key difference between Engram and Mnemos?

Engram belongs to the Knowledge & Memory category with local stdio execution, while Mnemos belongs to the Knowledge & Memory category with local stdio execution.

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

Engram operates under a Free / Open Source model (No auth required). Mnemos operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Engram lists 6 tools with 2 views and 7 GitHub stars. Mnemos lists 6 tools with 1 views and 11 GitHub stars.

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

Engram is listed under a Free / Open Source model with No auth required . Mnemos operates under a Free / Open Source model with No auth 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 and Mnemos at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both hbarefoot-engram and s60yucca-mnemos 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 has a Quality Score of 56 /100 ( Good ) with 2 views, 0 installs, and 7 GitHub stars. Mnemos holds a Quality Score of 44 /100 ( Fair ) with 1 views, 0 installs, and 11 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Engram vs Mnemos

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

Knowledge & Memory · Local stdio

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

Mnemos

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Engram if you need specialized Knowledge & Memory tools running via a local process. Choose Mnemos 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 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: engram_remember, engram_recall, engram_forget.

Explore Engram Details

Choose Mnemos 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: Single Go binary with embedded SQLite and FTS5 search, MCP stdio transport compatible with multiple AI coding agents, Automatic quality gating, deduplication, summarization, and file linking.

Explore Mnemos Details

Feature & Specification Comparison

Specification	Engram HBarefoot Knowledge & Memory	Mnemos s60yucca Knowledge & Memory
Summary	Local-first persistent memory for AI agents. SQLite + local embeddings (all-MiniLM-L6-v2), hybrid semantic + FTS5 recall, secret detection, and contradiction handling. 6 MCP tools (remember, recall, forget, feedback, context, status) over stdio. Zero cloud, no API keys, fully offline. Works with Claude Desktop/Code, Cursor, and Windsurf. npm install -g @hbarefoot/engram	Persistent memory engine for AI coding agents. Stores architecture decisions, bug root causes, and project conventions across sessions. Single Go binary with embedded SQLite, FTS5 search, context assembly within token budgets, and autopilot setup for Claude Code, Kiro, and Cursor.
Category & Scope

Tools & Capabilities Breakdown

Engram Tools (6)

engram_remember

Store a memory with category, entity, confidence, namespace, tags. Auto-runs secret detection.

engram_recall

Hybrid semantic + FTS5 search. Supports `category`, `namespace`, `threshold`, and `time_filter`.

engram_forget

Delete a specific memory by ID.

engram_feedback

Vote a memory helpful/unhelpful. Drives the feedback loop above.

engram_context

Pre-formatted context block (`markdown` / `xml` / `json` / `plain`) with a token budget for system-prompt injection.

engram_status

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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "hbarefoot-engram": {
      "command": "npx",
      "args": [
        "-y",
        "hbarefoot-engram"
      ]
    }
  }
}

Mnemos Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "s60yucca-mnemos": {
      "command": "npx",
      "args": [
        "-y",
        "s60yucca-mnemos"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Engram More alternatives to Mnemos Knowledge & Memory category hub