No user-submitted related servers found.
Scored across 30 tools
Most tools target a clearly distinct resource+action (generate vs check SBOM, list vs search components, add vs remove components, build vs test project), and descriptions are unusually detailed. The only genuinely overlapping clusters are the three migration-oriented tools (reassemble/upgrade/migrate) and the several 'add/assemble' tools, where boundaries are subtle though still differentiated by description.
Every tool follows a strict snake_case verb_noun pattern with a consistent 'egovframe' namespace token (list_egovframe_templates, add_egovframe_components, migrate_egovframe_project, etc.). The lone deviation (generate_agents_md, which drops the namespace token) still adheres to the same verb_noun convention, so predictability is essentially unbroken.
At 30 tools this exceeds the 25+ 'too many' band, and although the domain is broad, the surface includes near-duplicate workflow tools (three component-assembly tools, two catalog/template sync tools, three generate-report/ci/agents tools). The count is heavy enough that an agent must scan a large menu to pick the right operation.
Coverage of the scaffolding-to-migration lifecycle is strong: create project, add/remove/upgrade/reassemble components, migrate 3.x/4.x to 5.x, validate, diagnose, generate config/CRUD/report/CI/AGENTS.md, build, test, plus SBOM and docs tooling. Only minor gaps exist (e.g., no project deletion and config generation is one-way with no edit tool), which agents can work around.