Skip to main content
Glama
Sign In
NetBox MCP Server

NetBox MCP Server

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to NetBox MCP Server

No user-submitted related servers found.

    Related Servers

    • NetBox MCP Server

      NetBox MCP Serverofficial

      netboxlabs
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for NetBox that enables LLMs to query NetBox objects (devices, IPAM, etc.) and change logs through natural language, with field filtering for token optimization.
      4
      254
      Apache 2.0

    • NetBox MCP Server - Read &

      alexkiwi1
      A
      license
      A
      quality
      F
      maintenance
      Enables comprehensive interaction with NetBox infrastructure management through both read and write operations. Supports full CRUD operations for devices, IP addresses, sites, racks, and other NetBox objects through natural language commands.
      9
      18
      Apache 2.0

    • NetBox MCP Server

      jseifeddine
      A
      license
      B
      quality
      D
      maintenance
      Enables read-only interaction with NetBox network documentation and infrastructure data through LLMs. Allows querying devices, sites, IP addresses, and viewing change history via natural language.
      3
      Apache 2.0

    • netbox-mcp

      msemino
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that exposes NetBox IPAM data over HTTP, allowing engineers to query subnets, IPs, and VLANs using natural language through AI assistants.
      MIT

    • NetBox MCP Server

      chadkunsman
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only FastMCP server that enables AI assistants to query and retrieve network infrastructure information from NetBox using natural language.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read vs. write vs. specialized operations (trace, render, changelogs) are well separated. The main overlap is between netbox_get_objects (filtered list) and netbox_search_objects (cross-type q search), and to a lesser degree netbox_graphql_query, which can also list objects; descriptions help but an agent may still hesitate over which listing tool to use.

    Naming Consistency4/5

    Names follow a consistent netbox_verb_noun snake_case pattern (get_objects, create_object, bulk_update_objects). Minor deviations exist: netbox_graphql_query is noun_verb rather than verb_noun, and netbox_get_available is verb_adjective without a clear noun, but overall the convention is predictable.

    Tool Count4/5

    18 tools is slightly heavy but justified by NetBox's broad domain (DCIM, IPAM, circuits, virtualization) and the need for both single and bulk operations. Each tool has a recognizable purpose, though a few (e.g., separate search and list tools) could potentially be consolidated.

    Completeness4/5

    Core CRUD and bulk variants are present, plus specialized read operations (changelog, GraphQL, free-pool lookup, cable trace, config render) that cover most NetBox workflows. Minor gaps exist (e.g., no dedicated upsert or multi-ID get, and bulk read is only via filtered list), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources