NetBox is automatable through its API

NetBox is automatable today through its REST API. The NetBox Labs REST overview says the API uses HTTP and JSON for create, retrieve, update, and delete. The root is /api/, split into circuits, DCIM, extras, IPAM, plugins, tenancy, users, and virtualization. A running instance publishes Swagger UI at /api/schema/swagger-ui/. v2 tokens, the default, are sent as Authorization Bearer with the nbt_ prefix, the key, a period, and the secret. Legacy v1 tokens use Authorization Token and are deprecated, with removal planned in NetBox v5.0. Writes require a token that has write ability. NetBox Labs also documents a Platform MCP Server on every NetBox Cloud plan at https://INSTANCE.cloud.netboxapp.com/mcp. The client sends Authorization Bearer with an nbt_ token. Query and search are on every plan. Create, update, and delete require Starter or higher. Code Mode, IP allocation, cable tracing, and branching require Professional or higher. Enterprise support is described as a future release. The separate netboxlabs/netbox-mcp-server repository, pushed on 2026-10-16, is a read-only server. GitHub reported Apache-2.0 and archived false. The netbox-community/netbox repository is Apache-2.0. Connector catalogs were not opened. Computer-use viability is unassessed. The API scores 8. The Cloud MCP server scores 7 because it is official and broad, and the write tools are plan-gated. The API is the best path because it runs on a self-hosted NetBox instance as well as Cloud.

Best path today: api · Overall automatability: 8/10