Model Context Protocol (MCP) server for read-only interaction with NetBox data in LLMs
Model Context Protocol (MCP) server for read-only interaction with NetBox data in LLMs. That is what the netbox mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This is a simple read-only Model Context Protocol server for NetBox. It enables you to interact with your data in NetBox directly via LLMs that support MCP.
The server publishes 4 tools. What each one is for:
get_objects — Retrieves NetBox core objects based on their type and filtersget_object_by_id — Gets detailed information about a specific NetBox object by its IDget_changelogs — Retrieves change history records (audit trail) based on filtersRequirements — The Requirements tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: NETBOX_URL, NETBOX_TOKEN, ENABLE_PLUGIN_DISCOVERY, TRANSPORT, HOST, PORT, MCP_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. NetBox's toolset — get_objects, get_object_by_id, get_changelogs and 1 more — is a fair guide to whether it matches your workflow. It is maintained by netboxlabs; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_objects | Retrieves NetBox core objects based on their type and filters |
| get_object_by_id | Gets detailed information about a specific NetBox object by its ID |
| get_changelogs | Retrieves change history records (audit trail) based on filters |
| Requirements | The Requirements tool exposed by this server. |
{
"mcpServers": {
"netbox": {
"command": "uv",
"args": ["--directory", "/path/to/netbox-mcp-server", "run", "netbox-mcp-server"],
"env": {
"NETBOX_URL": "https://netbox.example.com/",
"NETBOX_TOKEN": "<your-api-token>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NETBOX_URL | Endpoint or connection string the server talks to. | Yes |
| NETBOX_TOKEN | Credential the server authenticates with. | Yes |
| ENABLE_PLUGIN_DISCOVERY | Configuration value read at startup. | Optional |
| TRANSPORT | Configuration value read at startup. | Optional |
| HOST | Endpoint or connection string the server talks to. | Optional |
| PORT | Configuration value read at startup. | Optional |
| MCP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.