What is the key difference between Mem0 MCP Selfhosted and Genesys Memory?

Mem0 MCP Selfhosted belongs to the Knowledge & Memory category with local stdio execution, while Genesys Memory belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mem0 MCP Selfhosted or Genesys Memory 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 Mem0 MCP Selfhosted and Genesys Memory free or paid?

Mem0 MCP Selfhosted operates under a Free / Open Source model (other). Genesys Memory operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mem0 MCP Selfhosted lists 11 tools with 3 views and 107 GitHub stars. Genesys Memory lists 13 tools with 0 views and 27 GitHub stars.

Can I use both Mem0 MCP Selfhosted and Genesys Memory 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

Mem0 MCP Selfhosted vs Genesys Memory

In-depth architectural comparison of the Mem0 MCP Selfhosted and Genesys Memory 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

Mem0 MCP Selfhosted

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: other

Genesys Memory

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Mem0 MCP Selfhosted if you need specialized Knowledge & Memory tools running via a local process. Choose Genesys Memory 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 Mem0 MCP Selfhosted when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: MEM0_USER_ID.
Primary tools included: add_memory, search_memories, get_memories.

Explore Mem0 MCP Selfhosted Details

Choose Genesys Memory 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: memory_store, memory_amend, memory_recall.

Explore Genesys Memory Details

Feature & Specification Comparison

Specification	Mem0 MCP Selfhosted elvismdev Knowledge & Memory	Genesys Memory Knowledge & Memory
Summary	Self-hosted mem0 MCP server for Claude Code with Qdrant vector search, Neo4j knowledge graph, and Ollama embeddings. Zero-config OAT auth, split-model graph routing, session hooks for automatic cross-session memory, and 11 tools. Supports both Anthropic and fully local Ollama setups.	Open-source causal memory for AI agents: persistent, explainable, MCP-native memory (13 tools).
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Mem0 MCP Selfhosted Tools (11)

add_memory

Store text or conversation history as memories. Supports `enable_graph`, `infer`, `metadata`.

search_memories

Semantic search with optional `filters`, `threshold`, `rerank`, `enable_graph`.

get_memories

List/filter memories (non-search). Supports `limit` and scope filters.

get_memory

Fetch a single memory by UUID.

update_memory

Replace memory text. Re-embeds and re-indexes in Qdrant.

delete_memory

Delete a single memory by UUID.

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

Mem0 MCP Selfhosted Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "elvismdev-mem0-mcp-selfhosted": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/elvismdev/mem0-mcp-selfhosted.git",
        "mem0-mcp-selfhosted"
      ],
      "env": {
        "MEM0_USER_ID": "YOUR_MEM0_USER_ID_HERE"
      }
    }
  }
}

Genesys Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "genesys-memory": {
      "command": "uvx",
      "args": [
        "papez"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Mem0 MCP Selfhosted More alternatives to Genesys Memory Knowledge & Memory category hub