No user-submitted related servers found.
Scored across 59 tools
Many tools overlap in search/discovery (find_files, search_in_files, find_replace, workspace_search, topology_search, workspace_symbols), file reading (read_file, read_multiple_files, read_symbol, file_outline), and editing (edit_file, write_file, transaction_apply, symbol insertion tools). Descriptions help distinguish scope and intent, but the volume and similarity create real misselection risk. An agent can usually find the right tool, but not without careful reading.
All names use snake_case and many carry clear domain prefixes (topology_, file_, workspace_, session_), making the set predictable. However, the pattern is not strictly verb_noun throughout: several tools are noun-first (file_outline, call_hierarchy, topology_status) or use other orderings. The deviations are minor and readable.
59 tools is an extreme mismatch for a single MCP server, far beyond the typical 3–15 well-scoped range and crossing the 50+ threshold. Even accounting for plumb's broad code-workspace purpose, the surface is heavily overloaded. Many tools could be consolidated or moved to separate servers.
The surface covers an unusually broad domain: file operations, git, LSP, topology analysis, memory, collaboration, tasks, diagnostics, and config. Minor gaps exist (e.g., no explicit directory-creation tool, no dedicated memory-update distinct from overwrite), but core lifecycle operations are present and workable.