Documentation MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_analyze_projectA | Analyze project structure and perform deep code analysis to understand the project for documentation generation. Supports TypeScript, JavaScript, Python, Go, and more. Deep analysis extracts classes, functions, interfaces, documentation coverage, and more. |
| docs_generate_structureB | Generate documentation scaffold/structure based on project analysis. Creates initial directory structure and configuration files. |
| docs_create_pageB | Create or edit individual documentation pages with Markdown content |
| docs_generate_apiC | Generate API documentation from code (JSDoc, Docstrings, etc.) |
| docs_build_staticA | Build static website for online hosting (ready for GitHub Pages, Netlify, Vercel, etc.) |
| docs_export_pdfB | Generate PDF from documentation using Puppeteer/Playwright |
| docs_previewB | Start local development server to preview documentation |
| docs_generate_openapiA | Generate OpenAPI 3.0 specification from analyzed PHP routes with middleware, parameters, and security schemes. Automatically converts controller routes to API documentation. |
| docs_generate_sales_docsB | Generate professional sales-ready documentation for CodeCanyon, ThemeForest, and other marketplaces. Creates comprehensive Markdown documentation (README, Installation, API Reference, Configuration, Examples, FAQ, Changelog) with optional PDF export. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: analysis, building static site, creating/editing pages, PDF export, API doc generation (two types), sales doc generation, structure scaffolding, and preview. No overlap that would confuse an agent.
All tools use the consistent 'docs_' prefix and follow a verb_noun pattern in snake_case (e.g., docs_analyze_project, docs_generate_api). No mixing of conventions.
9 tools is well-scoped for a documentation server. It covers the full workflow from analysis to generation, editing, preview, and export without being excessive.
The set covers core documentation tasks, but missing tools for listing/deleting pages or managing versions. Minor gap, but overall surface is solid.