// MCP TOOL REFERENCE

DOCUMCP TOOLS

52 tools from the Documcp MCP Server, categorised by risk level.

// ALL 52 DOCUMCP TOOLS

READ 28 tools

Read analyze_deployments Analyze deployment patterns and generate insights from historical deployment data Read analyze_readme Comprehensive README analysis with length assessment, structure evaluation, and optimization opportunities Read analyze_repository Analyze repository structure, dependencies, and documentation needs Read check_documentation_links Comprehensive link checking for documentation deployment with external, internal, and anchor link validation Read detect_documentation_gaps Analyze repository and existing documentation to identify missing content and gaps Read evaluate_readme_health Evaluate README files for community health, accessibility, and onboarding effectiveness Read get_community_insights Aggregate cross-project signals from the Knowledge Graph and surface community-level insights: deployment s... Read memory_contextual_search Perform contextual memory retrieval with intelligent ranking Read memory_enhanced_recommendation Get enhanced recommendations using learning and knowledge graph Read memory_insights Get insights and patterns from memory Read memory_intelligent_analysis Get intelligent analysis with patterns, predictions, and recommendations Read memory_knowledge_graph Query the knowledge graph for relationships and paths Read memory_learning_stats Get comprehensive learning and knowledge graph statistics Read memory_optimization_metrics Get comprehensive optimization metrics and recommendations Read memory_recall Recall memories about a project or topic Read memory_similar Find similar projects from memory Read memory_temporal_analysis Analyze temporal patterns and trends in memory data Read memory_visualization Generate visual representations of memory data Read read_directory List files and directories within allowed roots. Use this to discover files without requiring full absolute... Read readme_best_practices Analyze README files against best practices checklist and generate templates for improvement Read recommend_ssg Recommend the best static site generator based on project analysis and user preferences Read track_documentation_freshness Scan documentation directory for staleness markers and identify files needing updates based on configurable... Read validate_content Validate general content quality: broken links, code syntax, references, and basic accuracy Read validate_diataxis_content Validate the accuracy, completeness, and compliance of generated Diataxis documentation Read validate_readme_checklist Validate README files against community best practices checklist with detailed scoring Read verify_deployment Verify and troubleshoot GitHub Pages deployment Read memory_export Export memories to JSON or CSV Read memory_export_advanced Advanced memory export with multiple formats and options

WRITE 16 tools

Write optimize_readme Optimize README content by restructuring, condensing, and extracting detailed sections to separate document... Write populate_diataxis_content Intelligently populate Diataxis documentation with project-specific content Write record_drift_outcome Record the host Write sync_code_to_docs Automatically synchronize documentation with code changes using AST-based drift detection (Phase 3) Write validate_documentation_freshness Validate documentation freshness, initialize metadata for files without it, and update timestamps based on ... Write generate_config Generate configuration files for the selected static site generator Write generate_contextual_content Generate context-aware documentation using AST analysis and knowledge graph insights (Phase 3) Write generate_llm_context Generate a comprehensive LLM context reference file documenting all tools, memory system, and workflows for... Write generate_readme_template Generate standardized README templates for different project types with best practices Write manage_preferences Manage user preferences for documentation generation and SSG recommendations Write manage_sitemap Generate, validate, and manage sitemap.xml as the source of truth for documentation links. Sitemap.xml is u... Write memory_agent_network Manage multi-agent memory sharing and collaboration Write memory_import_advanced Advanced memory import with validation and conflict resolution Write setup_playwright_tests Generate Playwright E2E test setup for documentation site (containers + CI/CD) Write setup_structure Create Diataxis-compliant documentation structure Write update_existing_documentation Intelligently analyze and update existing documentation using memory insights and code comparison

DESTRUCTIVE 3 tools

Destructive cleanup_agent_artifacts Detect, classify, and clean up artifacts generated by AI coding agents (e.g., TODO.md, PLAN.md, agent marke... Destructive memory_cleanup Clean up old memories Destructive memory_pruning Intelligent memory pruning and optimization

EXECUTE 5 tools

Execute change_watcher Watch code changes and trigger documentation drift detection in near real-time. Execute deploy_pages [DEPRECATED — use deploy_site instead] Set up GitHub Pages deployment workflow. This alias will be removed ... Execute deploy_site Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and preference learning. Use... Execute memory_migration Create and execute migration plans between different memory systems Execute test_local_deployment Test documentation build and local server before deploying to GitHub Pages

// FAQ

How many tools does the Documcp MCP server have? +

The Documcp MCP server exposes 52 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Documcp tools? +

Route the Documcp server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Documcp tools fall into? +

Documcp tools are categorised as Read (28), Write (16), Destructive (3), Execute (5). Each category has a recommended default policy.

Enforce policy on every Documcp tool call.

Start from Documcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.