Is this related to an existing feature request or issue?
#1193
Summary
Deprecate the Code Documentation Generation MCP Server and guide users to native LLM tool capabilities that now accomplish this task more effectively.
Use case
This MCP Server was created because LLMs struggled with comprehensive documentation - only generated basic READMEs, poor monorepo understanding, no structured multi-file docs.
With LLM and other tools improvement, now available:
- Native tools to read/list files.
- Direct prompting generates comprehensive docs: "Generate docs including README, deployment guide, and API docs"
- Alternative ways to provide reusable workflows, such as Amazon Q Rules, Cline Rules, Claude Skills, and Kiro Powers.
Technical Issues:
- Repomix subprocess timeouts (120s in MCP vs 10s in shell)
- Uses only ~5% of repomix output (directory tree + stats)
- Over-engineered: 4-tool workflow for what simple prompting accomplishes
Proposal
Phase 1: Deprecation Notice (Day 1)
- Update README with deprecation banner
- Add in-tool warnings when functions are called
Phase 2: Archive (Day 30+)
Migration Guidance for Users
Instead of using this MCP server's 4-tool workflow, users should:
-
Direct Prompting (Recommended): Simply ask your AI assistant to "Generate comprehensive documentation for this project including README, deployment guide, and API docs." The LLM uses native tools automatically.
-
**Amazon Q Rules ** and Cline Rules: Create documentation rules with project-specific documentation templates and structure.
-
Claude Skills / Kiro Powers: Define reusable documentation generation workflows in your AI assistant.
Out of scope
N/A
Potential challenges
| Challenge |
Impact |
Mitigation |
| Users may not see deprecation notice |
Continue using broken/deprecated tool |
• In-tool warnings when functions are called
• README banner |
| CI/CD pipeline breakage after archive |
Automated documentation generation fails |
• 90-day notice period for updates
• Examples of alternative approaches |
Dependencies and Integrations
No response
Alternative solutions
Approach: Keep server, replace repomix with custom Python (~50 lines), simplify to 1-2 tools
Pros: Minimal change, existing users happy
Cons: Doesn't address fundamental question of whether tool provides value; ongoing maintenance burden
Is this related to an existing feature request or issue?
#1193
Summary
Deprecate the Code Documentation Generation MCP Server and guide users to native LLM tool capabilities that now accomplish this task more effectively.
Use case
This MCP Server was created because LLMs struggled with comprehensive documentation - only generated basic READMEs, poor monorepo understanding, no structured multi-file docs.
With LLM and other tools improvement, now available:
Technical Issues:
Proposal
Phase 1: Deprecation Notice (Day 1)
Phase 2: Archive (Day 30+)
Migration Guidance for Users
Instead of using this MCP server's 4-tool workflow, users should:
Direct Prompting (Recommended): Simply ask your AI assistant to "Generate comprehensive documentation for this project including README, deployment guide, and API docs." The LLM uses native tools automatically.
**Amazon Q Rules ** and Cline Rules: Create documentation rules with project-specific documentation templates and structure.
Claude Skills / Kiro Powers: Define reusable documentation generation workflows in your AI assistant.
Out of scope
N/A
Potential challenges
• README banner
• Examples of alternative approaches
Dependencies and Integrations
No response
Alternative solutions
Approach: Keep server, replace repomix with custom Python (~50 lines), simplify to 1-2 tools Pros: Minimal change, existing users happy Cons: Doesn't address fundamental question of whether tool provides value; ongoing maintenance burden