A
licenseNot graded
qualityD
maintenanceEnables AI agents to read and write a local-first knowledge base of plain markdown files in git, with governance gates for safe, hash-anchored edits.
1
Apache 2.0
Context Grove
Related Servers
Alternatives to Context Grove
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run automated daily code reviews, retrieve Markdown reports, and curate a project knowledge base across any Git repository.AGPL 3.0
docs-mcpofficial
AlicenseAqualityDmaintenanceLets AI agents search and read a folder of Markdown documentation at query time, exposing heading-level search, whole-page or section retrieval, and page listing as tools and resources over stdio or Streamable HTTP. Can run as a CLI, a hosted endpoint, or a library inside an existing Node or Next.js site.3725 npmMIT- AlicenseAqualityCmaintenanceEnables agents to search, read, list, and amend a git-backed markdown knowledge base, automatically committing and publishing changes.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides long-lived, cross-project technical memory for AI agents via markdown cards stored in git and indexed by SQLite, enabling search, retrieval, and human-reviewed knowledge management.ISC
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query and maintain source-bound project knowledge with git-computed freshness verdicts and a gated write path, providing trusted, up-to-date documentation for legacy codebases.1Apache 2.0
TDQS
A3.5/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a clearly distinct operation: availability check, catalog listing, document reading, and text search. There is no meaningful overlap between health, catalog, read, and search in this read-only knowledge context.
Naming Consistency5/5
All tool names follow the same predictable snake_case pattern with a shared knowledge_ prefix. The suffixes vary between resource and action words, but the overall convention is consistent and readable.
Tool Count5/5
Four tools are well-scoped for a read-only project knowledge source. Each tool earns its place by covering a distinct part of the access lifecycle: availability, discovery, retrieval, and search.
Completeness5/5
The surface covers checking availability, listing canonical areas and documents, reading by path, and searching with cited snippets. For a read-only knowledge access interface, this is complete with no obvious dead ends.