grepnotes
Related Servers
Alternatives to grepnotes
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search local notes by meaning and keyword using BM25 plus local Ollama embeddings, returning ranked paths and snippets verified against disk.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search and ask questions about a local codebase with citations, using BM25 and optional embeddings, all offline.3 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to search locally indexed code and research notes, returning file, line, and source-link references without external accounts or API keys.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve content from local Markdown notes using term-frequency scoring.2ISC
- AlicenseNot gradedqualityCmaintenanceEnables agents to search and retrieve past workspace conversations, dialogue transcripts, and markdown artifacts through local BM25 retrieval, providing cross-conversation architectural recall with low-latency, offline operation.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI hosts and agents to search, ask, and retrieve cited sections from a locally indexed collection of notes, documents, PDFs, web pages, org files, and chat logs using hybrid vector and BM25 retrieval.-
TDQS
Scored across 3 tools
Each tool targets a distinct access pattern: search_notes returns ranked passages, read_note returns one full document by path, and list_notes gives an inventory with headings. The descriptions explicitly contrast them (e.g. 'use this instead of reading whole files'), leaving no plausible misselection.
All three tools follow a clean verb_noun pattern (search_notes, read_note, list_notes) with a consistent 'note(s)' object noun and lowercase snake_case throughout.
Three tools is on the lean end but each covers a genuinely distinct retrieval mode for a focused read-only notes server. No obvious bloat, though the surface is thin enough that one more lifecycle tool (e.g. index/refresh) would round it out.
List, search, and read form a coherent read-only browsing workflow with no dead ends for querying an indexed knowledge base. Minor gaps exist: there is no way to add/refresh indexed documents or inspect metadata such as timestamps, so the index itself must be managed elsewhere.