No user-submitted related servers found.
Scored across 48 tools
There is real overlap in the note-querying family: search, query_documents, search_paths, list_documents, count_documents and aggregate_documents all answer 'find notes', and only careful reading of the descriptions separates them. Similarly get_context is explicitly a superset of get_backlinks/get_outlinks/get_similar, and the app-only vault_* tools duplicate read/search/list_documents for the SPA. The descriptions do a lot of work to disambiguate ('use X instead when...'), which keeps it from scoring lower.
Most names are snake_case, but the verb conventions are mixed: bare verbs (read, search, write, edit, append, delete, fetch, stats, reindex), get_/list_ prefixed tools, plus okf_*, vault_* and embeddings_status as noun-style names. The okf_ and vault_ prefixes are meaningful groupings, so it stays readable, but there is no single predictable pattern.
48 tools (roughly 41 LLM-visible once the app-only vault_* and context-card tools are excluded) is heavy for a markdown vault server, and several of them are narrow variants of one another (count_documents, aggregate_documents, search_paths, query_documents). The surface feels like it accumulated features rather than being scoped deliberately.
Coverage is genuinely broad: CRUD (read/write/edit/append/rename/delete/move_folder), link analysis (backlinks, outlinks, broken links, orphans, hubs, connection paths), git history/diff, indexing, embeddings, OKF tooling and fetch. Minor gaps remain — no folder deletion, no dedicated frontmatter-edit tool, and attachment discovery is only implicit — but nothing that blocks typical workflows.