MCP Index Notes
Related Servers
Alternatives to MCP Index Notes
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables semantic search, connection discovery, and grounded synthesis across your Apple Notes using on-device embeddings and optional LLM synthesis, with direct SQLite access for fast indexing.7 npm8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and interact with a graph database of markdown notes, extracting entities like wikilinks, mentions, and hashtags.MIT
- FlicenseNot gradedqualityDmaintenanceEnables to create notebooks and notes with tags, and perform full-text search across notes using FTS5 syntax, all stored locally in SQLite.-
- AlicenseAqualityBmaintenanceEnables users to create, retrieve, update, delete, and full-text search a local knowledge base of notes persisted in SQLite with FTS5, exposed over stdio or authenticated Streamable HTTP. It also surfaces recent/single-note resources and prompts for summarizing notes and drafting replies.5MIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides graph-based semantic memory storage and retrieval using vector embeddings and SQLite, enabling relationship creation between memories and similarity-based search through natural language.27 npm-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants like Claude and Codex to read, write, search, and traverse Markdown notes stored in a self-hosted knowledge base.3 npmMIT
TDQS
Scored across 16 tools
Most tools have distinct purposes, but some overlap exists: 'graph-neighbors' and 'graph-path' both involve graph traversal, which could cause minor confusion. However, descriptions clarify that 'graph-neighbors' retrieves connected nodes while 'graph-path' finds specific paths, helping to differentiate them. Other tools like 'index-query' and 'index-list-keys' are clearly separate in function.
Tool names follow a highly consistent pattern throughout, using a clear 'category-action' format (e.g., 'graph-import-from-notes', 'image-delete', 'index-backup'). This consistency makes it easy to predict tool purposes and group related operations, with no deviations or mixed conventions observed.
With 16 tools, the count is slightly high but reasonable for the server's scope, which covers graph operations, image management, and note indexing. It feels comprehensive without being overwhelming, though a few tools like 'index-health' might be considered optional, slightly reducing efficiency.
The tool set provides complete coverage for the domain of note and graph management, including CRUD operations (e.g., upsert, delete, get), querying, backup/restore, and health checks. There are no obvious gaps; agents can perform full lifecycles for notes, images, and graph nodes without dead ends.