No user-submitted related servers found.
Scored across 24 tools
Each tool targets a distinct phase or concern of Kotlin development—localization, dependencies, UI, backend, security, docs, etc.—so an agent can reliably pick the right one. The closest pairs, such as generate_and_run_tests versus generate_compose_screenshot_tests, are still clearly separated by scope.
All tool names use snake_case with a leading verb and consistently follow a verb_kotlin_<target> or verb_<domain> pattern. Even with varied verbs like generate, scaffold, audit, design, configure, and diagnose, the naming convention is predictable and uniform.
24 tools is on the heavy side for a single server, exceeding the ideal 3–15 range. However, each tool maps to a distinct Kotlin development task, so the count is defensible even though the server feels broad rather than lean.
The server covers the full Kotlin project lifecycle: prompt decomposition, dependency resolution, UI/backend/database/auth scaffolding, API contracts, tests, CI/CD, docs, security, observability, accessibility, and offline resilience. There are no obvious dead ends or critical missing operations for its stated purpose.