MCP Docs Server
Related Servers
Alternatives to MCP Docs Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI models to seamlessly access and query local markdown technical documentation files, providing automatic documentation context without explicit prompting.3 npm5ISC
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct access to local Markdown documentation libraries, enabling them to list, read, and search through docs on demand.MIT
- FlicenseAqualityCmaintenanceEnables MCP-compatible clients to search and read local markdown documentation, allowing agents to retrieve relevant doc snippets or full files by path.2-
- AlicenseAqualityCmaintenanceEnables AI assistants to search, retrieve, and browse Markdown documentation in a local folder, then answer questions with cited sources.6MIT
- AlicenseAqualityAmaintenanceEnables AI agents to discover, read, search, and install Markdown-based knowledge (rules, skills, workflows) from a local directory via MCP tools.13187 npm1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_docs' has a clear and distinct purpose that cannot be confused with any other tool in the set.
The single tool follows a consistent verb_noun pattern with 'search_docs'. Since there is only one tool, the naming is inherently consistent with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'MCP Docs Server', which suggests a documentation-focused domain. This minimal set lacks basic operations like retrieving, creating, updating, or deleting documents, making it feel thin and incomplete for the apparent scope.
The tool set is severely incomplete for a documentation server. While 'search_docs' provides a useful function, there are obvious gaps such as no CRUD operations (e.g., get_doc, create_doc, update_doc, delete_doc) or other lifecycle management tools, which will likely cause agent failures in handling documentation tasks.