documcp
Related Servers
Alternatives to documcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceComprehensive documentation lifecycle management powered by an MCP server. Automates documentation creation, maintenance, quality assessment, and synchronization for software projects.86MIT
- AlicenseNot gradedqualityDmaintenanceTransforms any GitHub repository or GitHub Pages site into a documentation hub for AI assistants using the Model Context Protocol. It allows AI tools to access real-time code and documentation to prevent hallucinations and provide accurate API usage examples.42 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that fetches documentation from public git repositories at specific versions, enabling AI coding assistants to access up-to-date, ref-pinned docs from source repos.5 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceSmart documentation generator and intelligent versioning system with full MCP support, enabling AI assistants like Claude and Gemini to manage project snapshots, generate docs, and control versioning via 26 MCP tools.1MIT
- AlicenseNot gradedqualityDmaintenanceA project-agnostic MCP server that exposes Markdown documentation from a project's /docs folder as MCP resources for AI agents. It provides stable, up-to-date context to reduce hallucinations and ensure agents remain aligned with project-specific conventions and goals.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceA documentation MCP server that crawls websites and Git repositories, stores them as Markdown, and provides tools to search and retrieve documentation for local LLMs and AI agents.Apache 2.0
TDQS
Scored across 52 tools
Many memory_* tools have overlapping purposes (e.g., memory_recall, memory_contextual_search, memory_similar, memory_insights all retrieve/analyze memories), and there are multiple validation tools (validate_diataxis_content, validate_content, validate_readme_checklist) that could cause misselection. The boundaries between these tools are not clearly distinct, leading to ambiguity.
The majority follow verb_noun (e.g., analyze_repository, generate_config), but the memory_* group is inconsistent—some are verb-noun (memory_recall), others are adjective-noun (memory_similar), and there's a deprecated alias (deploy_pages) alongside deploy_site. Mixed conventions and occasional non-verb patterns reduce predictability.
52 tools is excessive for a documentation MCP server. The core workflow (analysis, SSG, generation, deployment, validation) could be covered with 10-15 tools; the large memory_* cluster and multiple overlapping validation tools inflate the surface and make it unwieldy for an agent to navigate.
The server covers a broad range: repository analysis, SSG recommendation, configuration, structure setup, content generation, validation, deployment, README analysis, memory management, and drift detection. While some operations like deleting documentation are absent, the coverage is extensive and few critical gaps are apparent for the stated purpose.