No user-submitted related servers found.
Scored across 446 tools
Every tool embeds an action and a resource name, so the CRUD operations for a given object are usually clear. However, the set is full of near-parallel taxonomies like role/device_role/asset_role/contact_role and console_port/console_server_port/power_port/power_outlet/front_port/rear_port, with boilerplate descriptions that do little to differentiate them. Agents must parse subtle resource names carefully to avoid selecting the wrong endpoint.
Names overwhelmingly follow a consistent netbox_<verb>_<resource> pattern in snake_case, with list_/get_ and singular/plural forms used predictably. The single netbox_global_search outlier deviates from the verb-first pattern, and several resource names are lexically similar, so the convention is strong but not flawless.
446 tools is an extreme mismatch for an MCP server, far beyond the 25+ threshold for 'too many'. Exposing full CRUD for over a hundred resource types floods the agent's tool-selection context and makes finding the right operation impractical. A curated subset or grouped resource access would be far more usable.
For the resources that are exposed, coverage is remarkably complete: nearly every object type has list, get, create, update, and delete operations, plus cross-resource global_search. Gaps exist for non-exposed NetBox areas such as custom fields, tags, config contexts, and user management, and there are no bulk operations, but core DCIM/IPAM/circuit/inventory workflows are supported end-to-end.