Memory MCP Server for Zed
A Zed extension that provides a persistent knowledge graph through the Model Context Protocol. It wraps the official @modelcontextprotocol/server-memory package, giving your AI assistant long-term memory across sessions.
Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
A Zed extension that provides a persistent knowledge graph through the Model Context Protocol. It wraps the official @modelcontextprotocol/server-memory package, giving your AI assistant long-term memory across sessions.
Memory MCP server for the Zed editor 🧠
The extension exposes the following tools to the assistant:
zed: extensions in the command palette)Add the following to the MCP's settings to configure the memory file location:
{
"settings": {
"memory_file_path": "/absolute/path/to/memory.jsonl"
}
}
Note: The path must be absolute. Tilde expansion (
~) is not supported.
If memory_file_path is left empty (the default), the memory file is stored next to the server's index.js inside Zed's extensions directory.
Memories are stored as a knowledge graph in a JSONL file. Each line is a JSON object representing either an entity or a relation:
The assistant can read and write to this graph, allowing it to remember facts about you, your projects, preferences, and anything else across conversations.
wasm32-wasip1 target:
rustup target add wasm32-wasip1
zed: install dev extension in the command paletteZed will compile the extension and load it automatically. Changes to the source require reinstalling the dev extension.
MIT
Memory MCP server for the Zed editor 🧠
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Zed MCP Memory s'exécute en local via stdio.
Dernière vérification : 2026-10-28. Memory MCP server for the Zed editor 🧠