Obsidian Memory MCP is a server that stores AI memories as Markdown files designed for visualization in Obsidian's graph view. It transforms AI memory structures into individual Markdown files with Obsidian-compatible link syntax, allowing you to create an interactive knowledge graph of entities and their relationships.
Setting up the Obsidian Memory MCP server is straightforward:
git clone https://github.com/YuNaga224/obsidian-memory-mcp.git
cd obsidian-memory-mcp
npm install
npm run build
After installation, you need to configure Claude Desktop to use the MCP server:
{
"mcpServers": {
"obsidian-memory": {
"command": "node",
"args": ["/full/path/to/obsidian-memory-mcp/dist/index.js"],
"env": {
"MEMORY_DIR": "/path/to/your/obsidian/vault"
}
}
}
}
Make sure to replace the paths with the actual locations on your system. The MEMORY_DIR
environment variable should point to your Obsidian vault where you want the memory files to be stored.
Each entity is stored as an individual Markdown file with:
[[links]]
for relationsExample entity file structure:
---
entityType: person
created: 2025-07-10
updated: 2025-07-10
---
# John Doe
## Observations
- Works at Tech Corp
- Expert in TypeScript
- Lives in Tokyo
## Relations
- [[Manager of::Alice Smith]]
- [[Collaborates with::Bob Johnson]]
- [[Located in::Tokyo Office]]
When viewed in Obsidian's graph view, your knowledge base will be visualized with:
[[links]]
appearing as edges between nodesThe server exposes several tools you can use through Claude Desktop:
create_entities
: Create new entitiesdelete_entities
: Delete entities and related datacreate_relations
: Create relations between entitiesdelete_relations
: Remove relationsadd_observations
: Add observations to existing entitiesdelete_observations
: Remove specific observationsread_graph
: Get the entire knowledge graphsearch_nodes
: Search entities by queryopen_nodes
: Get specific entities by nameBy using these tools through Claude Desktop, you can build, maintain, and navigate your knowledge graph, which will be automatically visualized in Obsidian.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "obsidian-memory" '{"command":"node","args":["/full/path/to/obsidian-memory-mcp/dist/index.js"],"env":{"MEMORY_DIR":"/path/to/your/obsidian/vault"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"obsidian-memory": {
"command": "node",
"args": [
"/full/path/to/obsidian-memory-mcp/dist/index.js"
],
"env": {
"MEMORY_DIR": "/path/to/your/obsidian/vault"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"obsidian-memory": {
"command": "node",
"args": [
"/full/path/to/obsidian-memory-mcp/dist/index.js"
],
"env": {
"MEMORY_DIR": "/path/to/your/obsidian/vault"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect