Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
P

pinkpixel-dev/mem0-mcp

Long-term memory for agents, as a drop-in mem0 server

Before you install: no copy-paste command · no license recorded · link reachable

First step: npx -y @smithery/cli install @pinkpixel-dev/mem0-mcp-server --client claude

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
  "mcpServers": {
    "pinkpixel-dev-mem0-mcp": {
      "command": "npx",
      "args": ["-y", "@pinkpixel/mem0-mcp"]
    }
  }
}

Parsed from the README we fetched on 2026-11-04; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
  "servers": {
    "pinkpixel-dev-mem0-mcp": {
      "command": "npx",
      "args": ["-y", "@pinkpixel/mem0-mcp"]
    }
  }
}
Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio pinkpixel-dev-mem0-mcp -- npx -y @pinkpixel/mem0-mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
Source
collected from the abordage/awesome-mcp list · type: MCP server
Harvest history
first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
Score
score 1,003 · 10 sources · mcp
Install
npx -y @pinkpixel/mem0-mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx -y @pinkpixel/mem0-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# @pinkpixel/mem0-mcp MCP Server ✨

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

A Model Context Protocol (MCP) server that integrates with Mem0.ai to provide persistent memory capabilities for LLMs. It allows AI agents to store and retrieve information across sessions.
This server uses the mem0ai Node.js SDK for its core functionality.
## Features 🧠
### Modernized & Advanced Tools (v0.8.0)
addmemory: Stores a memory from text content or structured message arrays.
Inputs: content (string) or messages (array of role/content objects), userId (string), runId / sessionId (string), agentId (string), appId (string), metadata (object), infer (boolean), customInstructions (string), waitForCompletion (boolean, default: true), timeoutMs (number, default: 15000)
Behavior: Cloud V3 additions are asynchronous. By default, this tool polls the background queue until completed. Pass waitForCompletion: false to get the eventId immediately.
searchmemories: Searches memories using semantic and BM25 hybrid filters.
Inputs: query (string), userId (string), runId / sessionId (string), agentId (string), appId (string), filters (object), threshold (number), topK (number), rerank (boolean), referenceDate (string)
Behavior: Automatically nests scope variables inside the V3 filters block to prevent API validation errors.
searchmemory: Backward-compatible alias for searchmemories.
listmemories: Paginated listing of memory records scoped by identifiers.
Inputs: userId (string), runId / sessionId (string), agentId (string), appId (string), filters (object), page (number), pageSize (number)
getmemory: Retrieves a single memory record by its ID.
Inputs: memoryId (string)
updatememory: Modifies the text or metadata of an existing memory.
Inputs: memoryId (string), text (string), metadata (object)
deletememory: Deletes a specific memory record by ID.
Inputs: memoryId (string)
getmemoryhistory: Retrieves the audit trail of memory revisions (cloud only).
Inputs: memoryId (string)
getmemorycapabilities: Exposes the feature matrix and support flags of the active backend storage mode.
Inputs: None
batchupdatememories: Performs bulk updates of text contents for multiple memories (cloud only).
Inputs: updates (array of { memoryId: string, text: string } objects)
batchdeletememories: Performs bulk deletions of multiple memories.
Inputs: memoryIds (array of strings), confirm (boolean, must be true to execute)
ratememory: Submits quality feedback evaluation for a memory record (cloud only).
Inputs: memoryId (string), feedback (string: positive, negative, verynegative), reason (string, optional)
getmemoryevent: Manually retrieves details of a specific background event job (cloud only).
Inputs: eventId (string)
listmemoryevents: Lists history logs of background memory processing events (cloud only).
Inputs: page (number), pageSize (number)
creatememoryexport: Initiates an asynchronous memory export query job (cloud only).
Inputs: schema (object), filters (object, optional), exportInstructions (string, optional)
getmemoryexport: Retrieves status and download metadata of a memory export job (cloud only).
Inputs: exportId (string)
## Prerequisites 🔑
This server supports three storage modes:
1. Cloud Storage Mode ☁️ (Recommended for production)
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/pinkpixel-dev-mem0-mcp/)
Source
awesome · https://github.com/pinkpixel-dev/mem0-mcp
Browse by field
MCP servers
Listed by
10 independent sources
added
today

More like this

All 6,229 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index