What is the key difference between Heirmos and Mneme?

Heirmos belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Mneme belongs to the Knowledge & Memory category with local stdio execution.

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

Heirmos operates under a Free / Open Source model (No auth required). Mneme operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Heirmos lists 0 tools with 0 views and 0 GitHub stars. Mneme lists 0 tools with 0 views and 0 GitHub stars.

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

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

Yes! MCP clients support multi-server orchestration. You can include both heirmos and mneme 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, Heirmos has a Quality Score of 29 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Mneme holds a Quality Score of 28 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Heirmos vs Mneme

In-depth architectural comparison of the Heirmos and Mneme 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

Heirmos

Knowledge & Memory · Remote HTTP/SSE

Quality: 29/100 (Emerging) | Auth: No auth required

Mneme

Knowledge & Memory · Local stdio

Quality: 28/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Heirmos if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Mneme 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 Heirmos when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Heirmos Details

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

Explore Mneme Details

Feature & Specification Comparison

Specification	H Heirmos Knowledge & Memory	M Mneme Knowledge & Memory
Summary	Persistent memory shared across Claude, ChatGPT, Grok and other MCP clients.	Vault-native, accountable memory for Claude Code and MCP clients. Markdown is ground truth.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Heirmos Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Mneme Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Heirmos Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "heirmos": {
      "url": "https://heirmos.com"
    }
  }
}

Mneme Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Heirmos More alternatives to Mneme Knowledge & Memory category hub

Related MCP Server Comparisons

Popular comparisons with Heirmos

Popular comparisons with Mneme

Mneme vs Moxie Docs MCP