MCP Catalogs
Home

memory

Official

by modelcontextprotocol·85,748·Score 77

An MCP server implementing persistent memory using a local knowledge graph for AI models to remember user information across chats.

knowledge-graphai-llmproductivity
10,713
Forks
459
Open issues
this month
Last commit
2d ago
Indexed

Overview

The Memory MCP Server provides a robust implementation of persistent memory using a local knowledge graph architecture. It allows AI models like Claude to remember information about users across multiple conversations by storing entities, relations, and observations. The server exposes a comprehensive set of tools for creating and managing entities, relations, and observations within the knowledge graph, enabling sophisticated memory management. The implementation is well-structured with clear separation between entities (nodes), relations (edges), and observations (node attributes), providing flexibility in representing complex knowledge structures.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Personalizing AI assistant interactions by remembering user preferences, history, and relationships
you:Building context-aware chat applications that maintain conversation history
you:Creating knowledge bases that persist across AI model sessions
you:What storage format does the memory server use?
you:How does the server handle memory persistence across different AI model sessions?

When to choose this

Choose this server if you need persistent memory for an AI assistant to remember user information across chat sessions, especially when working with TypeScript-based environments or need a self-hosted solution without external dependencies.

When NOT to choose this

Avoid this for high-memory systems requiring complex reasoning capabilities beyond simple facts and relationships, or if you need integration with existing databases rather than file-based storage.

Tools this server exposes

9 tools extracted from the README
  • create_entities

    Create multiple new entities in the knowledge graph

  • create_relations

    Create multiple new relations between entities

  • add_observations

    Add new observations to existing entities

  • delete_entities

    Remove entities and their relations

  • delete_observations

    Remove specific observations from entities

  • delete_relations

    Remove specific relations from the graph

  • read_graph

    Read the entire knowledge graph

  • search_nodes

    Search for nodes based on query

  • open_nodes

    Retrieve specific nodes by name

Comparable tools

mcp-pineconemcp-neo4jvectordb-mcpmcp-redislocal-storage-mcp

Installation

Installation

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

VS Code

Use one-click installation buttons or manually configure in .vscode/mcp.json:

{
  "servers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    }
  }
}

Docker

{
  "mcpServers": {
    "memory": {
      "command": "docker",
      "args": ["run", "-i", "-v", "claude-memory:/app/dist", "--rm", "mcp/memory"]
    }
  }
}

FAQ

What storage format does the memory server use?
The server uses JSONL (JSON Lines) format for storing the knowledge graph data by default. The storage path can be customized using the MEMORY_FILE_PATH environment variable.
How does the server handle memory persistence across different AI model sessions?
The memory server maintains a persistent knowledge graph that survives between sessions. Entities, relations, and observations are stored in a local file and loaded when the server starts, allowing AI models to access accumulated information from previous interactions.

On Hacker News

Recent discussion from the developer community.

Compare memory with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.