chezmoi-documentation-mcp-server
Related Servers
Alternatives to chezmoi-documentation-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceIndexes documentation sites by base URL and serves keyword search, optional semantic search, and Markdown page retrieval as MCP tools, all from a single SQLite file.-
- FlicenseAqualityDmaintenanceEnables searching documentation from GitHub repositories and web pages via MCP tools, with in-memory indexing and caching for fast retrieval.3-
- AlicenseNot gradedqualityCmaintenanceEnables agents to search, retrieve, and list Hermes Agent documentation locally, version-matched to the installed commit, with fallback to GitHub when no local checkout exists.MIT
- AlicenseAqualityDmaintenanceEnables access to OpenTelemetry documentation by fetching and converting pages to markdown format and searching content using Google Custom Search. Provides comprehensive documentation lookup and search capabilities for OpenTelemetry concepts, instrumentation, and configuration.23Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to fetch live MDN Web Docs pages, TypeScript handbook content, and npm package metadata as clean markdown, with local search, caching, and polite throttling.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve live CPython standard-library documentation and PyPI package metadata as clean markdown, with cached, throttled, robots-aware requests and local module search.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct action: searching, reading a full page, reading specific sections, and listing available pages. There is no meaningful overlap between these operations.
All tool names follow a consistent verb_noun pattern (search_documentation, read_documentation, read_sections, list_documentation_pages), making the set predictable and easy to navigate.
Four tools is well-scoped for a documentation server, covering the essential tasks without unnecessary duplication. Each tool has a clear purpose and earns its place.
The tool surface covers the full workflow for documentation access: discovering pages, searching content, reading entire pages, and reading specific sections. No obvious gaps exist for the stated purpose.