How do I install the mem0 mcp selfhosted mcp server?

This profile does not contain a verified copy-paste launch configuration. Follow the current project documentation to confirm the runtime, entry point, transport and authentication before registering it in your client.

What credentials does it need?

It reads `MEM0_PROVIDER`, `MEM0_LLM_MODEL`, `MEM0_USER_ID`, `MEM0_LLM_URL`, `MEM0_EMBED_URL`, `MEM0_ANTHROPIC_TOKEN`, `ANTHROPIC_API_KEY`, `MEM0_OLLAMA_URL` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

SSyncDev

Start a project

Mem0 MCP Selfhosted MCP Server

Self-hosted [mem0](https://github.com/mem0ai/mem0) MCP server for Claude Code. Run a complete memory server against self-hosted Qdrant + Neo4j +

Remote serverstreamable-httpPython

What is the Mem0 MCP Selfhosted MCP Server?

Self-hosted mem0 MCP server for Claude Code. Run a complete memory server against self-hosted Qdrant + Neo4j + Ollama, with your

Credentials and setup notes

| Service | Required | Purpose | |---------|----------|---------| | Qdrant | Yes | Vector memory storage and search | | Ollama | Yes | Embedding generation (bge-m3) and optionally local LLM | | Neo4j 5+ | Optional | Knowledge graph (entity relationships) | | Google API Key | Optional | Required only for gemini/gemini_split graph providers | Python >= 3.10 and

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
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.
delete_all_memories	Bulk-delete all memories in a scope.
list_entities	List users/agents/runs with memory counts. Uses Qdrant Facet API.
delete_entities	Cascade-delete an entity and all its memories.
search_graph	Search Neo4j entities by name substring. Returns entities + outgoing relationships.
get_entity	Get all relationships for an entity (bidirectional: incoming + outgoing).

How to install the Mem0 MCP Selfhosted MCP Server

{
  "mcpServers": {
    "mem0": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/elvismdev/mem0-mcp-selfhosted.git",
        "mem0-mcp-selfhosted"
      ],
      "env": {
        "MEM0_PROVIDER": "ollama",
        "MEM0_LLM_MODEL": "qwen3:14b",
        "MEM0_USER_ID": "your-user-id"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

Variable	Description	Required
MEM0_PROVIDER	Declared in the maintainer’s client configuration.	Check documentation
MEM0_LLM_MODEL	Declared in the maintainer’s client configuration.	Check documentation
MEM0_USER_ID	Declared in the maintainer’s client configuration.	Check documentation

Example prompts to try

“Use Mem0 MCP Selfhosted to add memory.”
“Use Mem0 MCP Selfhosted to search memories.”
“Use Mem0 MCP Selfhosted to get memories.”

Frequently asked questions

Self-hosted [mem0](https://github.com/mem0ai/mem0) MCP server for Claude Code. Run a complete memory server against self-hosted Qdrant + Neo4j + Ollama, with your Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.