A
licenseC
qualityF
maintenanceMCP server for project management automation, providing tools for project health, documentation, task management, security scanning, and CI/CD validation.
27
1
MIT
Module Craft
by jacm-dev
Related Servers
Alternatives to Module Craft
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for automated architectural mapping, security vulnerability detection, ML asset tracking, and code metrics in local repositories.-
- FlicenseAqualityBmaintenanceMCP server that reviews and fixes code across four dimensions (security, standards, production readiness, sustainability), runs tests to verify fixes, and provides findings with diffs.1-
- AlicenseAqualityDmaintenanceMCP server for comprehensive code analysis, navigation, and quality assessment across 25+ programming languages.988MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides tools for architecture analysis, risk diagnosis, quality metrics, and regression guarding to support AI-driven code review and incremental refactoring workflows.5MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enforces development discipline and workflow best practices, guiding users through a structured process of coding, testing, documenting, committing, and releasing.63 npm1MIT
TDQS
B3.3/5.0
Scored across 10 tools
Disambiguation3/5
Most tools have clearly distinct purposes, but track_progress and evaluate_module_progress overlap significantly in tracking module status, and plan_module vs define_module_requirements could be confused for similar planning activities. Overall, descriptions reduce most ambiguity, but these pairs create potential misselection.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern, such as plan_module, analyze_code_quality, and generate_documentation. The naming convention is uniform and predictable across the entire set.
Tool Count5/5
The server has 10 tools, which is well-scoped for a module development workflow covering planning, requirements, analysis, documentation, validation, and progress tracking. Each tool contributes a distinct phase of the lifecycle without unnecessary bloat.
Completeness4/5
The toolset covers major module development phases well, from requirements and planning through quality, security, performance, accessibility, documentation, and progress validation. Minor gaps exist, such as no explicit tool for listing or selecting modules, and the overlap between progress-related tools leaves some lifecycle aspects somewhat redundant.
Maintenance
ActivityInactive
ResponsivenessNo issues