No user-submitted related servers found.
Scored across 40 tools
Multiple graph-query tools have unclear boundaries: query_ontology contains neighbors/path/impact/subgraph operations that overlap directly with find_neighbors, find_path, find_backlinks, and compile_ontology. The analysis tools also overlap heavily (analyze_repo_structure, infer_imports, index_project, inspect_architecture), so an agent must read long descriptions to choose correctly.
Most names follow a readable snake_case verb_noun pattern (list_concepts, add_relation, validate_vault, get_constellation). There are some noun-first exceptions such as connection_info, git_status, git_history, and git_snapshot, plus singular/plural batch pairs, but the convention remains largely predictable.
Forty tools is excessive for a single MCP server, exceeding the 25+ threshold where the surface becomes heavy and hard to navigate. The count is inflated by separate read/write/query/analysis tools plus batch variants, many of which could be consolidated or exposed as operations of fewer tools.
The ontology concept and relation lifecycle is well covered: create, batch create, read, batch read, patch, rename, reclassify, merge, delete, add/remove/replace relations, validation, compilation, repo analysis, and git checkpoints. Minor gaps remain around constellation lifecycle (list/get only, no save/update/delete) and wiki authoring (read/validate only).