home / mcp / basic memory mcp server
Provides a local, bidirectional knowledge graph with notes and semantic relationships accessible via MCP-enabled clients.
Configuration
View docs{
"mcpServers": {
"basicmachines-co-basic-memory": {
"command": "uvx",
"args": [
"basic-memory",
"mcp"
],
"env": {
"BASIC_MEMORY_ENV": "dev",
"BASIC_MEMORY_LOG_LEVEL": "DEBUG",
"BASIC_MEMORY_NO_PROMOS": "true",
"BASIC_MEMORY_CLOUD_MODE": "true",
"BASIC_MEMORY_FORCE_CLOUD": "true",
"BASIC_MEMORY_FORCE_LOCAL": "true",
"BASIC_MEMORY_EXPLICIT_ROUTING": "true"
}
}
}
}Basic Memory MCP Server enables seamless interaction between your local knowledge base and compatible AI models through the Model Context Protocol. You run a local MCP server that lets AI assistants read and write to your Markdown-based knowledge graph, while you retain full control over your data. This setup supports collaborative workflows, offline use, and future cloud options without mandatory reliance on remote services.
You interact with the MCP server by connecting an MCP-enabled client (such as Claude Desktop or a compatible editor) to the server. The client sends read and write requests to your local Markdown-based knowledge graph, and the server exposes a set of tools to navigate, create, edit, and query notes and the knowledge graph.
Prerequisites: ensure you have a compatible runtime and tooling installed on your machine.
# Install the MCP-capable client tool (example)
uv tool install basic-memoryConfigure the MCP server connection in your client. Use the following standard local server configuration, which runs the MCP server via the uvx command and forwards the basic-memory MCP endpoint.
{
"mcpServers": {
"basic_memory": {
"command": "uvx",
"args": ["basic-memory", "mcp"]
}
}
}You can also configure client integrations to enable per-project routing and cloud features when you choose to opt in. The MV configuration blocks shown above are designed to be pasted into your client’s MCP settings.
The server exposes a rich set of capabilities to manage and query your knowledge graph. Core tools include the following.
You can configure Claude Desktop to connect to the local MCP server by editing its MCP configuration to point to the local uvx-based server. You can also enable per-project routing, cloud features, and synchronization using the provided commands and flows.
Create or update notes with specified title, content, and optional folder or tags; supports output in text or JSON formats.
Read notes by title or permalink with support for pagination and formatting options.
Read raw file content from the knowledge base, including text, images, and binaries.
View notes as formatted artifacts suitable for display in clients.
Edit notes incrementally using operations like append, find_replace, or replace_section with optional JSON output.
Move notes between directories or destinations while preserving database consistency.
Delete notes from the knowledge base with optional output format.
Navigate the knowledge graph using memory:// URLs to fetch related context.
Retrieve recently updated information from the knowledge base.
Browse directory contents with filtering options.
Search across the knowledge base with optional pagination and filters.
Search notes with multiple filters, including query, tags, types, and project context.
List all available memory projects and their status.
Create a new memory project with a specified path.
Show statistics for the currently active project.
Check synchronization status between local files and the knowledge graph.
Provide an overview and setup guidance for optional cloud features.
Show the latest release notes for the MCP server.
Generate visualizations of knowledge graph nodes and edges.