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

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

Mem0 Mcp Selfhosted operates under a BYOK (Pay Provider Direct) model (API Key required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Mem0 Mcp Selfhosted lists 11 tools with 2 views and 104 GitHub stars. Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars.

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

Mem0 Mcp Selfhosted is listed under a BYOK (Pay Provider Direct) model with API Key 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 Mem0 Mcp Selfhosted and Moxie Docs MCP at the same time in my AI client?

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

Mem0 Mcp Selfhosted vs Moxie Docs MCP

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

Mem0 Mcp Selfhosted

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Mem0 Mcp Selfhosted 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 Mem0 Mcp Selfhosted when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MEM0_USER_ID, MEM0_PROVIDER, MEM0_LLM_MODEL, MEM0_LLM_URL, MEM0_EMBED_URL.
Primary tools included: add_memory, search_memories, get_memories.

Explore Mem0 Mcp Selfhosted 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	Mem0 Mcp Selfhosted elvismdev Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & 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.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

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

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"
      ],
      "env": {
        "MEM0_USER_ID": "YOUR_MEM0_USER_ID_HERE",
        "MEM0_PROVIDER": "YOUR_MEM0_PROVIDER_HERE",
        "MEM0_LLM_MODEL": "YOUR_MEM0_LLM_MODEL_HERE",
        "MEM0_LLM_URL": "YOUR_MEM0_LLM_URL_HERE",
        "MEM0_EMBED_URL": "YOUR_MEM0_EMBED_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

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

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