{
"mcpServers": {
"io-github-rog0x-docs": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
JSDoc, README, changelog generation for AI agents
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 18 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.rog0x/docs and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Documentation generation tools for AI agents, served via the Model Context Protocol (MCP).
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 |
npm install
npm run build
Add to your MCP client configuration:
{
"mcpServers": {
"docs-tools": {
"command": "node",
"args": ["path/to/mcp-docs-tools/dist/index.js"]
}
}
}
Parses a function signature and generates JSDoc/TSDoc with @param, @returns, @throws, and @example tags.
Parameters:
functionSignature (string, required) - The function signature to documentdescription (string, optional) - Description of the functionincludeExample (boolean, optional, default: true) - Whether to include an @example tagAnalyzes README content for required sections (Installation, Usage, License, etc.), rates completeness from 0-100, and suggests missing sections.
Parameters:
content (string, required) - Full text content of the README fileGenerates CHANGELOG entries from git-style commit messages following the Keep a Changelog format. Categorizes commits as Added, Changed, Fixed, Removed, Deprecated, or Security.
Parameters:
versions (array, required) - Array of { version, date, commits } objectsprojectName (string, optional) - Project name for the headerGenerates REST API documentation in Markdown from endpoint descriptions including method, URL, parameters, request/response examples, and status codes.
Parameters:
apiTitle (string, required) - Title for the API documentationbaseUrl (string, optional) - Base URL for the APIapiDescription (string, optional) - General API descriptionendpoints (array, required) - Array of endpoint definitionsAnalyzes source code comment coverage: computes comment-to-code ratio, finds TODO/FIXME/HACK markers, detects functions without documentation, and suggests where docs are needed.
Parameters:
code (string, required) - Source code to analyzelanguage (string, optional, default: "typescript") - Programming languageNo additional configuration required. The server runs over stdio.
MIT