Skip to main content
Glama
JSkier21

notesearch-mcp

by JSkier21

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTESEARCH_DATANoDirectory where the index is stored. Default: $XDG_DATA_HOME/notesearch$XDG_DATA_HOME/notesearch
NOTESEARCH_SKIPNoComma-separated file names to leave out of the index. Default: MEMORY.mdMEMORY.md
NOTESEARCH_NOTESNoPath 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_KEYNoOptional bearer token for the embedding server. Default: empty
NOTESEARCH_EMBED_URLNoOpenAI-compatible embeddings endpoint URL. Default: http://127.0.0.1:1234/v1/embeddingshttp://127.0.0.1:1234/v1/embeddings
NOTESEARCH_EMBED_MODELNoEmbedding model name. Changing this rebuilds the index automatically. Default: text-embedding-bge-m3-latesttext-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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

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).

Naming Consistency5/5

Both names follow the same verb_noun snake_case convention (search_notes, read_note). The pattern is predictable and self-documenting.

Tool Count3/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues