Datacron
Related Servers
Alternatives to Datacron
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA generic Markdown vault MCP server with FTS5 full-text search, semantic vector search, frontmatter-aware indexing, incremental reindexing, and non-markdown attachment support that exposes search, read, write, and edit tools.44228 PyPI34MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that enables full-text search and link navigation over Markdown files as a knowledge graph.-
- AlicenseBqualityCmaintenanceEnables hybrid dense and BM25 search over a markdown vault, with tools for reading, writing, grepping, and managing notes through any MCP-compatible client.12MIT
- AlicenseBqualityCmaintenancePython MCP server for programmatic access to markdown-based knowledge vaults, enabling AI assistants to browse, read, search, update, and manage notes, tasks, and projects.481MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server for retrieval over markdown wikilink vaults, offering hybrid vector+lexical search, note reading, neighbor expansion, and recent activity tracking with fully local embeddings and no network egress.MIT
- FlicenseCqualityCmaintenanceMCP server to query and modify an Obsidian vault or any folder of markdown files. It provides search, tag filtering, backlinks, and CRUD operations on notes, with path traversal protection.11-
TDQS
Scored across 22 tools
Most tools target distinct resource+action pairs (search_text vs search_regex, and the section editors patch/rename/delete/move are clearly differentiated). However there is a cluster of receipt/history tools (get_note_history, audit_query, get_write_progress) whose boundaries overlap and could be misselected, and prepare_follow_up vs get_follow_up require reading carefully to separate.
Predominantly consistent snake_case verb_noun pattern (get_note, list_notes, search_text, patch_note_section, delete_note_section, revert_note). A few outliers break the verb-first convention (audit_query, contradiction_scan, session_context), but they remain readable and predictable.
22 tools is on the heavy side, but for a full memory/vault server spanning search, read, structured writes, section editing, lifecycle, audit, and health, each tool maps to a defensible operation. Slightly over-scoped for a casual user but not wasteful.
Strong coverage: discovery (list/search/backlinks), reads (get_note with chunk/map/section modes), and a rich write surface (create, append, frontmatter lifecycle, section patch/rename/delete/move, revert), plus history/audit/health. Minor gaps like whole-note rename or folder-move are absent, though deletion is intentionally replaced by invalidation.