Skip to main content
Glama
mhajder

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 by netboxlabs

      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
      243
      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
      17
      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
      B
      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.8/5.0

    Scored across 18 tools

    Disambiguation4/5

    Each tool has a fairly distinct purpose, and descriptions clarify boundaries well (e.g. netbox_get_objects filters one type while netbox_search_objects queries multiple types with the 'q' filter). Minor overlap exists between the several read paths (get_objects, search_objects, graphql_query) and between get_available vs allocate_available, but the docs disambiguate them adequately.

    Naming Consistency5/5

    Every tool uses the same netbox_ prefix followed by a consistent verb_noun pattern (netbox_get_object(s), netbox_create_object, netbox_bulk_update_objects, netbox_delete_object). No mixing of conventions.

    Tool Count4/5

    18 tools is on the heavier side but earns its place given NetBox's breadth: single + bulk CRUD, discovery, search, GraphQL, cable tracing, config rendering, and IPAM allocation. The set is well-scoped with little redundancy.

    Completeness5/5

    Full lifecycle coverage is present: read (get/list/search/graphql), create/update/delete singles, bulk variants of each, plus discovery (list/describe types, status), changelogs, pool inspection/allocation, cable tracing and config rendering. No obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources