NetBox MCP Server
Related Servers
Alternatives to NetBox MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables an LLM to read and write NetBox data through its REST API, supporting listing endpoints, inspecting schemas, and creating, updating, or deleting objects.7-
- AlicenseBqualityAmaintenanceGives AI assistants read (and optionally write) access to a NetBox instance, covering DCIM, IPAM, circuits, virtualization, tenancy, and more.10019 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to create, read, update, and delete NetBox resources such as sites, networks, VLANs, IP addresses, devices, interfaces, cables, and VMs through generic CRUD and convenience tools, with automatic name/slug resolution and optional read-only or API-key protection.MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to read and manage NetBox network infrastructure data via MCP. Supports querying all object types, search, changelogs, GraphQL, IP/prefix/VLAN allocation, cable tracing, config rendering, and write operations with safety modes.18176 PyPI3MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Nautobot instances through schema-driven tools for CRUD operations, dependency planning, and GraphQL queries, efficiently handling large APIs without overwhelming agent context.Apache 2.0
- AlicenseAqualityFmaintenanceEnables comprehensive interaction with NetBox infrastructure management through both read and write operations. Supports full CRUD operations for devices, IP addresses, sites, racks, and other NetBox objects through natural language commands.918Apache 2.0
TDQS
Scored across 8 tools
Tools have largely distinct purposes: get_objects retrieves multiple objects with filters, get_object_by_id retrieves a single object by ID, and search_objects performs a global search. Some overlap exists between get_objects (with filters) and search_objects, as both can query multiple objects, but the descriptions clarify the difference (structured filtering vs. global text search).
All tool names follow a consistent snake_case pattern with the prefix 'netbox_' followed by a verb and noun (e.g., netbox_get_objects, netbox_create_object). This predictable convention makes the tool set easy to navigate.
With 8 tools, the set is well-scoped for interacting with NetBox. It covers essential operations (read, create, update, bulk operations, search, changelogs) without excessive fragmentation, aligning with the typical needs of an agent managing network infrastructure.
The server provides comprehensive CRUD coverage: create (single and bulk), read (get by filters, get by ID, search), and update (single and bulk). However, there is no delete operation, which is a notable gap for full lifecycle management, though agents might work around this by updating statuses or relying on other tools.