mcp-tool-docs-stinger

Prevent documentation drift by validating technical references against actual source code behavior, capturing MCP handler schemas, outputs, side effects, and TypeScript exports to keep published references aligned. This source-first validation ensures docs match real implementation.

Document MCP tool schemas and side effects accurately by extracting tool names, purposes, input schemas, outputs, and examples directly from the source code. This source-first approach ensures the generated reference matches actual handler behavior.

TypeDoc generation for CLI command references works by guiding the extraction of TypeScript public APIs and command behavior into synchronized documentation. This process maintains doc-to-code alignment and enforces changelog discipline for release updates.

Yes, you can audit existing MCP documentation against the source code by running synchronization checks that compare published references with actual MCP handlers and TypeScript exports. This validation captures discrepancies and updates docs to match implementation.

Yes, TypeScript source files are required to maintain MCP API references because the documentation process validates public APIs, CLI commands, and tool schemas against the actual source code behavior to ensure accurate, code-aligned references.

Source-first documentation validation for MCP tools relies on direct access to current source code, meaning it cannot accurately document deprecated handlers or behaviors without corresponding code present in the repository for synchronization checks.