NetBox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETBOX_URL | Yes | The URL of your NetBox instance | |
| NETBOX_TOKEN | Yes | Your NetBox API token with read permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| netbox_get_objectsB | Get objects from NetBox based on their type and filters Args: object_type: String representing the NetBox object type (e.g. "devices", "ip-addresses") filters: dict of filters to apply to the API call based on the NetBox API filtering options Valid object_type values: DCIM (Device and Infrastructure):
IPAM (IP Address Management):
Circuits:
Virtualization:
Tenancy:
VPN:
Wireless:
See NetBox API documentation for filtering options for each object type. |
| netbox_get_object_by_idC | Get detailed information about a specific NetBox object by its ID. Args: object_type: String representing the NetBox object type (e.g. "devices", "ip-addresses") object_id: The numeric ID of the object Returns: Complete object details |
| netbox_get_changelogsA | Get object change records (changelogs) from NetBox based on filters. Args: filters: dict of filters to apply to the API call based on the NetBox API filtering options Returns: List of changelog objects matching the specified filters Filtering options include:
Example: To find all changes made to a specific device with ID 123: {"changed_object_type_id": "dcim.device", "changed_object_id": 123} To find all deletions in the last 24 hours: {"action": "delete", "time_after": "2023-01-01T00:00:00Z"} Each changelog entry contains:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: netbox_get_changelogs retrieves audit logs of changes, netbox_get_object_by_id fetches a single object by ID, and netbox_get_objects lists objects by type with filtering. There is no overlap in functionality, making it easy for an agent to select the right tool for each task.
All tool names follow a consistent snake_case pattern with the prefix 'netbox_' and a descriptive verb_noun structure: get_changelogs, get_object_by_id, get_objects. This uniformity makes the tool set predictable and easy to understand at a glance.
With only three tools, the server feels thin for the broad domain of NetBox, which includes many object types across DCIM, IPAM, circuits, virtualization, tenancy, VPN, and wireless. While the tools cover basic read operations, the count is borderline low given the extensive scope implied by the object_type list.
The tool set is severely incomplete for a NetBox server, as it only provides read operations (get) with no support for create, update, or delete. This leaves significant gaps in CRUD/lifecycle coverage, which will likely cause agent failures when trying to perform common administrative tasks like adding devices or modifying IP addresses.