No user-submitted related servers found.
Scored across 114 tools
Distinct domain prefixes (browser_, chrome_, lsp_, vscode_, pty_, job_) and detailed descriptions help, but there are multiple overlapping suites for similar actions, such as browser_* vs chrome_* and run_command vs process_start vs job_start. An agent can usually pick correctly from context, yet the parallel tool families create real misselection risk.
Most tools use snake_case with a predictable domain prefix and action-oriented names, especially browser_, chrome_, windows_, lsp_, vscode_, pty_, job_, and process_. There are minor deviations like outline, batch, repo_map, and project_context, but the overall naming pattern is readable and mostly consistent.
The server exposes 114 tools, far beyond the 3–15 range for a well-scoped set. Even with broad coding-agent capabilities, this volume makes discovery, selection, and maintenance unusually heavy.
The surface is very broad: file editing, code search, LSP, terminals, background jobs, browser and Chrome automation, Windows UI automation, video recording, git, web search, and project memory. Some lifecycle gaps remain, such as git branch/push/pull/merge operations and dedicated test/package management, but most agent workflows are covered.