Docs
Automates documentation generation across five distinct tools: JSDoc comment creation from function signatures, README completeness analysis with scoring, changelog generation from git commits following Keep a Changelog format, REST API documentation from endpoint definitions, and code comment coverage analysis that surfaces TODOs and undocumented functions. Runs over stdio and requires no configuration. Reach for this when you need structured documentation output during development workflows, especially if you're working with AI agents that need to generate or evaluate docs programmatically. The analyze_readme tool rates completeness 0-100 and flags missing sections, while generate_api_docs handles request/response examples and status codes automatically.
- tools
- 5
- transport
- STDIO
- last updated
- Mar 22, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
generate_jsdocParses a function signature and generates JSDoc/TSDoc with @param, @returns, @throws, and @example tags.
Parses a function signature and generates JSDoc/TSDoc with @param, @returns, @throws, and @example tags.
No parameter schema in public metadata yet.
analyze_readmeAnalyzes README content for required sections (Installation, Usage, License, etc.), rates completeness from 0-100, and suggests missing sections.
Analyzes README content for required sections (Installation, Usage, License, etc.), rates completeness from 0-100, and suggests missing sections.
No parameter schema in public metadata yet.
generate_changelogGenerates CHANGELOG entries from git-style commit messages following the Keep a Changelog format.
Generates CHANGELOG entries from git-style commit messages following the Keep a Changelog format.
No parameter schema in public metadata yet.
generate_api_docsGenerates REST API documentation in Markdown from endpoint descriptions including method, URL, parameters, request/response examples, and status codes.
Generates REST API documentation in Markdown from endpoint descriptions including method, URL, parameters, request/response examples, and status codes.
No parameter schema in public metadata yet.
analyze_code_commentsAnalyzes source code comment coverage: computes comment-to-code ratio, finds TODO/FIXME/HACK markers, detects functions without documentation, and suggests where docs are needed.
Analyzes source code comment coverage: computes comment-to-code ratio, finds TODO/FIXME/HACK markers, detects functions without documentation, and suggests where docs are needed.
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
mcp-docs-tools
Documentation generation tools for AI agents, served via the Model Context Protocol (MCP).
Overview
mcp-docs-tools provides five specialized documentation tools accessible through MCP:
| Tool | Description |
|---|---|
generate_jsdoc | Generate JSDoc/TSDoc comments from function signatures |
analyze_readme | Analyze README completeness and suggest improvements |
generate_changelog | Generate CHANGELOG entries from commit messages |
generate_api_docs | Generate REST API documentation from endpoint definitions |
analyze_code_comments | Analyze comment coverage, find TODOs, detect undocumented functions |
Installation
npm install
npm run build
Usage
As an MCP Server
Add to your MCP client configuration:
{
"mcpServers": {
"docs-tools": {
"command": "node",
"args": ["path/to/mcp-docs-tools/dist/index.js"]
}
}
}
Tools
generate_jsdoc
Parses a function signature and generates JSDoc/TSDoc with @param, @returns, @throws, and @example tags.
Details
- Repository
- github.com/rog0x/mcp-docs-tools
- Package
@rog0x/mcp-docs-tools- Transport
- STDIO
- Registry
- MCP registry, active