notes-rag-pg
Related Servers
Alternatives to notes-rag-pg
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI assistants with tools to create, list, search, tag, and delete notes stored in a local SQLite database.-
- FlicenseNot gradedqualityCmaintenanceEnables semantic search over personal study notes by exposing a vector search tool that Claude Desktop can call to retrieve relevant note content and synthesize grounded answers.-
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools to upsert and search vector-embedded note chunks, enabling semantic retrieval from a PostgreSQL/pgvector backend.MIT
- FlicenseNot gradedqualityAmaintenanceEnables semantic search over personal markdown notes by indexing them into a vector database and exposing search, reindex, and status tools via MCP.-
- AlicenseAqualityBmaintenanceEnables AI agents to store, full-text search, and organize notes with tags.7MIT
- AlicenseNot gradedqualityDmaintenanceProvides semantic search and keyword search over Obsidian notes, along with direct note retrieval, allowing external AI agents to query and access the vault.19BSD Zero Clause
TDQS
Scored across 2 tools
Each tool has a completely distinct purpose: one searches content, the other lists source files. There is no overlap in functionality or arguments, so an agent would never confuse them.
Both tools follow a clear verb_noun pattern: 'search_notes' and 'list_note_sources'. They use snake_case consistently and start with an imperative verb, making the naming predictable and intuitive.
With only two tools, the server feels minimal. While the scope (searching and listing notes) is narrow and could justify a lean surface, it is at the borderline where agents might benefit from additional operations like fetching a specific chunk or retrieving full notes.
For a read-only RAG server over class notes, the two tools cover the essential workflows: searching relevant content and listing available sources. There are no obvious missing operations that would cause an agent to get stuck in a typical use case.