documcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_repositoryC | Analyze repository structure, dependencies, and documentation needs |
| recommend_ssgA | Recommend the best static site generator based on project analysis and user preferences |
| generate_configC | Generate configuration files for the selected static site generator |
| setup_structureC | Create Diataxis-compliant documentation structure |
| setup_playwright_testsC | Generate Playwright E2E test setup for documentation site (containers + CI/CD) |
| deploy_siteA | Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and preference learning. Use the 'target' parameter to choose one deployment platform per project (github-pages or vercel). If you switch targets, the tool will warn you to remove the old workflow file. |
| deploy_pagesB | [DEPRECATED — use deploy_site instead] Set up GitHub Pages deployment workflow. This alias will be removed in v1.1.0. |
| verify_deploymentB | Verify and troubleshoot GitHub Pages deployment |
| populate_diataxis_contentC | Intelligently populate Diataxis documentation with project-specific content |
| update_existing_documentationC | Intelligently analyze and update existing documentation using memory insights and code comparison |
| validate_diataxis_contentB | Validate the accuracy, completeness, and compliance of generated Diataxis documentation |
| validate_contentB | Validate general content quality: broken links, code syntax, references, and basic accuracy |
| detect_documentation_gapsC | Analyze repository and existing documentation to identify missing content and gaps |
| test_local_deploymentB | Test documentation build and local server before deploying to GitHub Pages |
| evaluate_readme_healthB | Evaluate README files for community health, accessibility, and onboarding effectiveness |
| readme_best_practicesA | Analyze README files against best practices checklist and generate templates for improvement |
| check_documentation_linksB | Comprehensive link checking for documentation deployment with external, internal, and anchor link validation |
| generate_readme_templateB | Generate standardized README templates for different project types with best practices |
| validate_readme_checklistB | Validate README files against community best practices checklist with detailed scoring |
| analyze_readmeB | Comprehensive README analysis with length assessment, structure evaluation, and optimization opportunities |
| optimize_readmeB | Optimize README content by restructuring, condensing, and extracting detailed sections to separate documentation |
| manage_preferencesC | Manage user preferences for documentation generation and SSG recommendations |
| analyze_deploymentsC | Analyze deployment patterns and generate insights from historical deployment data |
| read_directoryA | List files and directories within allowed roots. Use this to discover files without requiring full absolute paths from the user. |
| sync_code_to_docsC | Automatically synchronize documentation with code changes using AST-based drift detection (Phase 3) |
| change_watcherB | Watch code changes and trigger documentation drift detection in near real-time. |
| record_drift_outcomeA | Record the host's judgment ('actionable' | 'noise' | 'deferred') for a previously-detected drift. Outcomes feed back into priority-scoring weights via the knowledge graph (ADR-012 Phase 4, Issue #114). |
| generate_contextual_contentC | Generate context-aware documentation using AST analysis and knowledge graph insights (Phase 3) |
| track_documentation_freshnessB | Scan documentation directory for staleness markers and identify files needing updates based on configurable time thresholds (minutes, hours, days) |
| validate_documentation_freshnessC | Validate documentation freshness, initialize metadata for files without it, and update timestamps based on code changes |
| manage_sitemapB | Generate, validate, and manage sitemap.xml as the source of truth for documentation links. Sitemap.xml is used for SEO, search engine submission, and deployment tracking. |
| generate_llm_contextC | Generate a comprehensive LLM context reference file documenting all tools, memory system, and workflows for easy @ reference |
| cleanup_agent_artifactsA | Detect, classify, and clean up artifacts generated by AI coding agents (e.g., TODO.md, PLAN.md, agent markers, temporary files). Supports scan, clean, and archive operations with configurable patterns. |
| get_community_insightsA | Aggregate cross-project signals from the Knowledge Graph and surface community-level insights: deployment success rates per SSG, common technology stacks, frequent drift sources, and project health distribution. All data is anonymized — no raw project paths are exposed. |
| memory_recallC | Recall memories about a project or topic |
| memory_intelligent_analysisC | Get intelligent analysis with patterns, predictions, and recommendations |
| memory_enhanced_recommendationC | Get enhanced recommendations using learning and knowledge graph |
| memory_learning_statsC | Get comprehensive learning and knowledge graph statistics |
| memory_knowledge_graphC | Query the knowledge graph for relationships and paths |
| memory_contextual_searchD | Perform contextual memory retrieval with intelligent ranking |
| memory_agent_networkC | Manage multi-agent memory sharing and collaboration |
| memory_insightsC | Get insights and patterns from memory |
| memory_similarB | Find similar projects from memory |
| memory_exportC | Export memories to JSON or CSV |
| memory_cleanupC | Clean up old memories |
| memory_pruningC | Intelligent memory pruning and optimization |
| memory_temporal_analysisD | Analyze temporal patterns and trends in memory data |
| memory_visualizationC | Generate visual representations of memory data |
| memory_export_advancedC | Advanced memory export with multiple formats and options |
| memory_import_advancedC | Advanced memory import with validation and conflict resolution |
| memory_migrationC | Create and execute migration plans between different memory systems |
| memory_optimization_metricsC | Get comprehensive optimization metrics and recommendations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tutorial-writer | Generate learning-oriented tutorial content following Diataxis principles |
| howto-guide-writer | Generate problem-oriented how-to guide content following Diataxis principles |
| reference-writer | Generate information-oriented reference documentation following Diataxis principles |
| explanation-writer | Generate understanding-oriented explanation content following Diataxis principles |
| diataxis-organizer | Organize existing documentation using Diataxis framework principles |
| readme-optimizer | Optimize README content using Diataxis-aware principles |
| analyze-and-recommend | Complete repository analysis and SSG recommendation workflow |
| setup-documentation | Create comprehensive documentation structure with best practices |
| troubleshoot-deployment | Diagnose and fix GitHub Pages deployment issues |
| maintain-documentation-freshness | Track and maintain documentation freshness with automated staleness detection |
| code-mode-documentation-setup | Complete documentation setup using code-based orchestration (Code Mode optimized) |
| code-mode-parallel-workflow | Execute multiple documcp operations in parallel for maximum efficiency (Code Mode optimized) |
| code-mode-efficient-analysis | Comprehensive project analysis with resource-based result filtering (Code Mode optimized) |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Static Site Generators | List of supported SSGs with capabilities for UI selection |
| Jekyll Configuration Template | Template for Jekyll _config.yml |
| Hugo Configuration Template | Template for Hugo config.yaml |
| Docusaurus Configuration Template | Template for Docusaurus docusaurus.config.js |
| MkDocs Configuration Template | Template for MkDocs mkdocs.yml |
| Eleventy Configuration Template | Template for Eleventy .eleventy.js |
| Diataxis Structure Template | Diataxis documentation structure blueprint |
| All Documentation Workflows | Complete list of available documentation workflows |
| Quick Documentation Setup Workflow | Fast-track workflow for basic documentation |
| Full Documentation Setup Workflow | Comprehensive workflow for complete documentation |
| Workflow Execution Guidance | Guidelines for executing documentation workflows |
| Documentation Freshness Presets | Available staleness threshold presets for UI selection (realtime, active, recent, weekly, monthly, quarterly) |
| Freshness Metadata Schema | Schema for documentation frontmatter freshness metadata fields |
| Community Insights | Aggregated cross-project insights: SSG success rates, common tech stacks, frequent drift sources, and project health — all anonymized |
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.