Gives AI agents read and write access to an Obsidian vault, with tools to list, read, search, create, edit, append, replace, archive, and restore notes, plus recent changes and task progress reporting.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
An MCP server that gives AI agents read and write access to a single Obsidian vault. It works directly on the Markdown files in a folder and speaks Streamable HTTP. It is stateless, so every request gets its own server and transport.
Tool | What it does |
| Lists notes and folders |
| Reads a note, with a version hash |
| Text search in file names and contents |
| Creates a new note, fails if it already exists |
| Replaces one exact piece of text (must be unique) |
| Adds text at the end, or under a heading |
| Overwrites the whole note, requires the version from the latest read |
| Lists notes changed in the last N days, newest first |
| Counts task checkboxes per note and per heading in a folder, with frontmatter |
| Moves a note to the archive folder |
| Moves a note from the archive folder to its original location |
Plus the resource vault://index, which lists every note.
Notes can be changed from other devices while an agent is working on them. edit_note fails if the text is no longer there, and replace_note fails if the version is stale. The agent then has to read the note again.
Related MCP server: Obsidian MCP
The server tells agents to read About the vault.md at the start of a session, if that note exists. Put it in the vault root and use it to describe the structure and conventions you want agents to follow: which folders exist, how tasks and links are written, and what agents may or may not change.
Only .md files
No access to hidden files and folders (.obsidian, .trash)
No .. or absolute paths, and symlinks cannot point outside the vault
No deleting. Notes can only be moved to and from _arkiv/
Atomic writes, at most 1 MB per write
The log shows which notes were touched, never their content
/mcp requires the header Authorization: Bearer <token>. The token is never accepted in the URL, and the server will not start without a valid MCP_TOKEN. /healthz is open and only responds with {"ok":true}.
Set as environment variables. See .env.example for a template.
Variable | Default | What it is |
| (required) | Path to the vault folder |
| (required) | At least 32 characters, only |
|
| Address the server listens on |
|
| Port the server listens on |
|
| Maximum size of a single write |
Requires Node 22.18 or newer. The code runs as TypeScript directly, with no build step.
npm install
cp .env.example .env # fill in VAULT_ROOT and MCP_TOKEN
npm run dev
npm run typecheck
npm run smoke # against a running server, creates _smoketest in the vault
npm run inspector # Streamable HTTP, URL http://127.0.0.1:3333/mcp, header Authorization: Bearer ...MIT, see LICENSE.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Search, read, and safely update Markdown notes in your connected Phasoric knowledge vaults.
Markdown notes in folders, with files, that your AI assistant can read, write and organise.
Markdown notes in folders, with files, that your AI assistant can read, write and organise.