No user-submitted related servers found.
Scored across 9 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, get_dev_logs retrieves logs, get_dev_status checks process state, and restart_dev_server restarts the process—each targets a specific action on a specific resource. There is no overlap in functionality that would cause misselection.
Tool names follow a consistent verb_noun pattern throughout, such as get_dev_logs, restart_dev_server, and scan_project_dirs. All tools use snake_case with descriptive verbs (e.g., get, restart, scan, start, stop), making them predictable and readable.
With 9 tools, the count is well-scoped for managing npm development processes and MCP server health. Each tool earns its place by covering distinct aspects like monitoring, control, recovery, and project scanning, without being excessive or insufficient for the domain.
The tool set provides complete lifecycle coverage for npm development and MCP server management. It includes monitoring (get_dev_status, get_health_status), control (start, stop, restart), recovery (auto_recover, recover_from_state), and utilities (scan_project_dirs, get_dev_logs), with no obvious gaps that would cause agent failures.