NetBox MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host address for HTTP server (required if TRANSPORT=http) | 127.0.0.1 |
| PORT | No | Port for HTTP server (required if TRANSPORT=http) | 8000 |
| LOG_LEVEL | No | Logging verbosity (DEBUG, INFO, WARNING, ERROR, CRITICAL) | INFO |
| TRANSPORT | No | MCP transport protocol (stdio or http) | stdio |
| NETBOX_URL | Yes | Base URL of your NetBox instance (e.g., https://netbox.example.com/) | |
| VERIFY_SSL | No | Whether to verify SSL certificates | true |
| NETBOX_TOKEN | Yes | API token for authentication | |
| ENABLE_PLUGIN_DISCOVERY | No | Auto-discover plugin object types at startup | false |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| netbox_get_objectsA |
|
| netbox_get_object_by_idB | Get detailed information about a specific NetBox object by its ID. |
| netbox_get_changelogsC | Get object change records (changelogs) from NetBox based on filters. |
| netbox_search_objectsA | |
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 4 tools
The four tools are mostly distinct: generic typed queries, single-object retrieval by ID, changelog queries, and global search. However, netbox_get_objects can approximate both netbox_get_object_by_id (with an id filter) and netbox_search_objects (with name filters), so an agent may occasionally need to choose carefully. Descriptions provide enough guidance to resolve most ambiguity.
All tools use a consistent snake_case pattern with the netbox_ prefix and a clear action verb: get_objects, get_object_by_id, get_changelogs, and search_objects. The single 'search' verb deviation is semantically appropriate and does not break predictability.
Four tools is on the low side but still reasonable for a focused NetBox query server, and the generic get_objects tool covers a very broad object surface. The set is well scoped for read/query workflows, though it feels slightly thin for a full NetBox integration.
The surface is entirely read-only: it supports listing, searching, retrieving by ID, and changelogs, but has no create, update, delete, or bulk mutation operations. For a NetBox server, this is a significant lifecycle gap that would block agents from managing infrastructure objects. Read coverage is strong, but CRUD completeness is missing.