Enterprise MCP Kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETBOX_TOKEN | Yes | NetBox API token | |
| NETBOX_BASE_URL | Yes | Base URL for NetBox (HTTP or HTTPS) | |
| NETBOX_TIMEOUT_MS | No | Timeout in milliseconds (default 5000) | 5000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_device_contextA | Read one exact NetBox device context. This tool performs no write operations. |
| get_site_overviewA | Read one exact NetBox site and a bounded summary of its devices, racks, active circuits, contacts, and software compliance. This tool performs no write operations. |
| get_connectivity_pathA | Read bounded NetBox circuit and VPN evidence directly connecting two exact sites. It does not claim a runtime routed path and performs no write operations. |
| get_rack_contextA | Read one exact NetBox rack by ID or exact site and rack name, including a bounded device elevation summary and recorded power-feed count. This tool performs no write operations. |
| get_power_pathA | Read bounded NetBox inventory evidence for what powers one exact device: its power ports, cabled PDU outlets, and recorded rack power feeds. It never claims live electrical state and performs no write operations. |
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 5 tools
Each tool targets a distinct read perspective—device context, site overview, site-to-site connectivity, rack context, and power path—so an agent can usually choose the right one. There is mild thematic overlap in site/rack/power summaries, but the bounded scopes keep the boundaries clear.
All tool names consistently begin with get_, making the read-only convention obvious and predictable. However, the suffixes vary between context, overview, and path, so the naming is not perfectly uniform.
Five tools is a focused and appropriate size for a read-only infrastructure visibility server. Each tool covers a meaningful query area without unnecessary redundancy.
The set covers the core infrastructure visibility concerns: site, device, rack, power, and site-to-site connectivity evidence. It lacks broader device-detail or circuit-list tools, but the bounded summaries avoid major dead ends for the apparent read-only scope.