Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"zed-mcp-server-basic-memory": {
"args": [
"uv"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This extension integrates Basic Memory as a context server for Zed Editor's Assistant.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'uv' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
uv vulnerable to arbitrary file deletion through RECORD entries
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall. uv does not use the RECORD fi
uv allows ZIP payload obfuscation through parsing differentials
### Impact In versions 0.9.5 and earlier of uv, ZIP archives were handled in a manner that enabled two parsing differentials against other components of the Python packaging ecosystem: 1. Central directory entries in a ZIP archive can contain comment fields. However, uv would assume that these fields were not present, since they aren't widely used. Consequently, a ZIP archive could be constructed where uv would interpret the contents of a central directory comment field as ZIP control structur
uv has differential in tar extraction with PAX headers
### Impact In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers. The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518. In practice, the impact of this vulnerability is **low**:
uv allows ZIP payload obfuscation through parsing differentials
## Impact In versions 0.8.5 and earlier of uv, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. This enabled two parser differentials against other Python package installers: 1. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. The attacker could choose which installer to target
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP Security Weekly
Get CVE alerts and security updates for Zed Mcp Server Basic Memory and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This extension integrates Basic Memory as a context server for Zed Editor's Assistant.
Basic Memory lets you build persistent knowledge through natural conversations with Large Language Models, while keeping everything in simple Markdown files on your computer.
⚠️ Important Note: This extension currently requires Zed to support MCP tools, which is still in development. While you can install the extension now, its functionality will become available once Zed adds MCP tools support in a future update. Follow Zed's releases for updates.
pip install uv
uv tool install basic-memory
Navigate to: Zed > Extensions. Or use the command palette to search for "extensions".
Add the following to your Zed settings:
{
"context_servers": {
"mcp-server-basic-memory": {
"settings": {
"project": "optional-project-name"
}
}
}
}
The project setting is optional:
~/basic-memory/config.json, or set in the BASIC_MEMORY_PROJECT environment variable)You can configure these settings either:
Once configured, Basic Memory will be available in the Zed Assistant. You can use prompts like:
Basic Memory supports multiple projects to separate different kinds of notes. If you work on different codebases or subjects, you might want to maintain separate knowledge bases for each.
This extension needs to be compiled to WebAssembly (WASM):
Add the WASM target to your Rust toolchain:
rustup target add wasm32-wasip1
Build the extension:
cargo build --target wasm32-wasip1 --release
For testing locally:
Note: When installing as a dev extension, Zed will automatically use the build artifacts from your target directory.
For more detailed information about Basic Memory, visit:
This project is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at:
http://www.apache.org/licenses/LICENSE-2.0
This extension interfaces with the basic-memory MCP server, which is a separate product developed by Basic Machines and is licensed under the GNU Affero General Public License, Version 3.0 (AGPL-3.0). The basic-memory MCP server's license can be found at:
https://www.gnu.org/licenses/agpl-3.0.html
Please note that while this extension is distributed under the Apache 2.0 License, if you use the basic-memory MCP server through this extension, you must comply with its AGPL-3.0 license terms. This extension itself does not incorporate any code from the basic-memory MCP server; it only provides an interface to comm