
Notes Vault
io.github.gronarePublished by GitHub account gronarev0.13.0Updated Nov 4, 2026
Indexed search, schema-checked writes and session hooks for a markdown notes vault
Overview
Notes Vault's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Notes Vault in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
notes-vault-mcp
Memory for Claude and coding agents, kept as markdown notes you own, with a schema that holds and a tie to your git history.
Install
A vault server with Docker Compose, for claude.ai, Claude Desktop, mobile and every machine you work on. You need a domain pointing at the machine, ports 80 and 443 open, and an SMTP account for sign-in links.
Then open https://VAULT_HOST/account and sign in. Install with Docker walks through each step.
Only Claude Code on one machine, with a local folder:
Use
Add the server's address, https://VAULT_HOST/mcp, as a custom connector in claude.ai. Claude searches, reads and writes your notes. The same search from a shell on a signed-in machine:
What you get
- Notes you own. Plain markdown in a folder or an S3 bucket; open them in Obsidian, keep them in git.
- A schema with teeth. Required fields, legal statuses and kinds, a tag vocabulary; a write that breaks the contract is refused. Start from PARA, a simple vault, a journal or your own layout.
- A lifecycle.
closearchives finished work,backlog_addfiles what was deferred,log_appendwrites one line per repo per session,lintreports drift. - Memory tied to code. A note names the paths it describes; the session-start hook prints the commits newer than the note.
- Search that reads your languages. Stemming, folded diacritics, synonyms, and optional search by meaning that runs on your machine.
- Your own vault server. Accounts with passkeys, email links, GitHub or your identity provider, several vaults each, shared vaults, sealed in storage.
Documentation
docs/ has the install guides, the how-tos for each client, the reference for every tool, command and setting, and how it works.
License
MIT. See LICENSE.
Source: README.md at commit 41ad2f4
Tools
0Version history
11- v0.13.0LatestNov 4, 2026
- v0.12.0Nov 3, 2026
- v0.9.2Nov 1, 2026
- v0.9.1Nov 1, 2026
- v0.9.0Nov 1, 2026
- v0.8.0Oct 23, 2026
- v0.7.0Oct 20, 2026
- v0.6.1Oct 20, 2026
- v0.5.1Oct 17, 2026
- v0.5.0Oct 6, 2026
- v0.4.5Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts