notesearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTESEARCH_DATA | No | Directory where the index is stored. Default: $XDG_DATA_HOME/notesearch | $XDG_DATA_HOME/notesearch |
| NOTESEARCH_SKIP | No | Comma-separated file names to leave out of the index. Default: MEMORY.md | MEMORY.md |
| NOTESEARCH_NOTES | No | Path to the folder of markdown notes to index. Default: ~/.claude/projects/<home path with / as ->/memory | ~/.claude/projects/<home path with / as ->/memory |
| NOTESEARCH_EMBED_KEY | No | Optional bearer token for the embedding server. Default: empty | |
| NOTESEARCH_EMBED_URL | No | OpenAI-compatible embeddings endpoint URL. Default: http://127.0.0.1:1234/v1/embeddings | http://127.0.0.1:1234/v1/embeddings |
| NOTESEARCH_EMBED_MODEL | No | Embedding model name. Changing this rebuilds the index automatically. Default: text-embedding-bge-m3-latest | text-embedding-bge-m3-latest |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search the user's long-term memory notes (markdown) by meaning and keywords. Returns the best-matching notes with a description and passage. Notes can be stale: verify before acting on them. Use read_note to open a whole note. |
| read_noteA | Return the full text of one memory note by file name, e.g. 'opnsense-dhcp-kea.md'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are complementary and non-overlapping: search_notes locates notes by meaning/keyword, and read_note opens one specific note by filename. Descriptions explicitly state the handoff between them (search first, then read the whole note).
Both names follow the same verb_noun snake_case convention (search_notes, read_note). The pattern is predictable and self-documenting.
Two tools is on the thin side for even a narrow server. It covers the search-and-open flow, but there is no room for supporting operations like listing or browsing notes.
Retrieval is covered end-to-end (find then read), but the memory domain has a notable gap: there is no way to create, update, or list notes, so an agent cannot persist or enumerate memories. It is workable if notes are written by other means, but the surface feels partial.