obsidian-connector
Provides tools for reading, writing, searching, and managing Markdown notes in an Obsidian vault, including listing notes and folders, reading note content, full-text and tag search, getting backlinks, creating and appending notes, managing daily notes, and updating YAML frontmatter.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@obsidian-connectorsearch notes tagged #meetings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Vault Connector for Obsidian
A local MCP connector that lets Claude read, write and search any Obsidian vault. It works directly with the Markdown files on disk — no community plugins, and Obsidian does not need to be running.
Independent project, not affiliated with or endorsed by Obsidian. "Obsidian" is a trademark of Dynalist Inc.
All access is sandboxed to the single vault folder you configure; the server refuses any path that would escape it.
Tools
Tool | Access | Description |
| read | List Markdown notes, optionally within a folder |
| read | List sub-folders of the vault or a folder |
| read | Read the full content of a note |
| read | Full-text and |
| read | Find notes linking to a target via |
| write | Create a note with optional YAML frontmatter |
| write | Append text to a note, optionally under a heading |
| write | Append an entry to today's (or a given date's) daily note |
| write | Set or remove YAML frontmatter fields |
Related MCP server: @kazuph/mcp-obsidian
Configuration
The server is configured through environment variables (set automatically from the connector settings when installed as a Desktop Extension):
Variable | Required | Default | Purpose |
| yes | — | Absolute path to the vault folder |
| no | `` (root) | Vault-relative folder for daily notes |
| no |
| Daily-note filename format ( |
Development
npm install
npm run build # compile TypeScript to dist/
npm run inspect # open the MCP Inspector against the serverTry it locally in Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"obsidian": {
"command": "node",
"args": ["/absolute/path/to/dist/index.js"],
"env": {
"OBSIDIAN_VAULT_PATH": "/absolute/path/to/your/Vault",
"OBSIDIAN_DAILY_FOLDER": "Log"
}
}
}
}Package as a Desktop Extension (.mcpb)
npm run pack # builds and produces obsidian-connector.mcpbThe resulting .mcpb can be installed in Claude Desktop with one click, or submitted to the
Claude connector directory via the
Desktop Extension submission form.
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/noragami90/obsidian-connector'
If you have feedback or need assistance with the MCP directory API, please join our Discord server