WTFM
OfficialRelated Servers
Alternatives to WTFM
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to document every app feature by turning browser sessions into structured, re-runnable App Flows with screenshots and steps, compiled into shareable support guides.MIT- AlicenseNot gradedqualityDmaintenanceAutomatically generates comprehensive wiki documentation from any codebase, including Mermaid diagrams, source code citations, and automated quality checks.3MIT
- AlicenseNot gradedqualityDmaintenanceGenerates comprehensive documentation (architecture overview, dependency graph, API surface, and README) for any codebase locally without external APIs.9 npm1MIT

Doc Bridgeofficial
AlicenseNot gradedqualityBmaintenanceTurn repository documentation into deterministic, executable handoffs for coding agents through MCP, CLI, and CI—without an LLM or API key.2,784 npm9MIT- AlicenseNot gradedqualityDmaintenanceProvides documentation generation and analysis tools for AI agents, including JSDoc generation, README analysis, changelog generation, API documentation, and code comment analysis.19 npmMIT
- AlicenseBqualityBmaintenanceAutomatically collects, summarizes, and documents code from vibe coding sessions, generating multiple document types (README, DESIGN, TUTORIAL, etc.) and publishing them to platforms like Notion, GitHub Wiki, and Obsidian.1532 npm1MIT
TDQS
Scored across 47 tools
Several tools are near-duplicates: find_article_gaps, suggest_sections, and recommend_articles share nearly identical descriptions, while list_sections/list_recommendations and review_sections/review_recommendations are hard to distinguish. setup_hosted and connect_repository are explicit aliases, and many article lifecycle tools overlap, making tool selection error-prone.
All tools use a consistent supportpages_ snake_case prefix, and most follow a verb_noun pattern. Minor deviations such as noun-style supportpages_doctor or the compatibility alias supportpages_connect_repository are readable but slightly less uniform.
47 tools is well above the ideal 3-15 range and feels over-fragmented for the domain. Many narrowly scoped lifecycle steps and duplicate analysis/list/review variants increase selection cost without clear proportional benefit.
Article handling covers a broad lifecycle: create, edit, list, get, validate, preview, finalize, upload, publish, unpublish, and delete. Video walkthroughs are less complete, with create/list/get but no obvious update, delete, or sharing operation, leaving minor gaps.