Skip to main content
Glama
ZenixSolutions

netbox-mcp-server

by ZenixSolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to netbox-mcp-server

No user-submitted related servers found.

    Related Servers

    • netbox-mcp

      David41186
      F
      license
      A
      quality
      B
      maintenance
      Enables an LLM to read and write NetBox data through its REST API, supporting listing endpoints, inspecting schemas, and creating, updating, or deleting objects.
      7
      -

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

      NetBox MCP Serverofficial

      netboxlabs
      A
      license
      A
      quality
      C
      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
      234
      Apache 2.0

    • New Relic MCP Server

      Meet-Bhalodiya
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to New Relic with read-only access to NRQL, logs, metrics, traces, alerts, and more. Offers optional, gated write operations with a dry-run and confirmation workflow.
      22 npm
      Apache 2.0
    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

    B3.4/5.0

    Scored across 446 tools

    Disambiguation3/5

    Every tool embeds an action and a resource name, so the CRUD operations for a given object are usually clear. However, the set is full of near-parallel taxonomies like role/device_role/asset_role/contact_role and console_port/console_server_port/power_port/power_outlet/front_port/rear_port, with boilerplate descriptions that do little to differentiate them. Agents must parse subtle resource names carefully to avoid selecting the wrong endpoint.

    Naming Consistency4/5

    Names overwhelmingly follow a consistent netbox_<verb>_<resource> pattern in snake_case, with list_/get_ and singular/plural forms used predictably. The single netbox_global_search outlier deviates from the verb-first pattern, and several resource names are lexically similar, so the convention is strong but not flawless.

    Tool Count1/5

    446 tools is an extreme mismatch for an MCP server, far beyond the 25+ threshold for 'too many'. Exposing full CRUD for over a hundred resource types floods the agent's tool-selection context and makes finding the right operation impractical. A curated subset or grouped resource access would be far more usable.

    Completeness4/5

    For the resources that are exposed, coverage is remarkably complete: nearly every object type has list, get, create, update, and delete operations, plus cross-resource global_search. Gaps exist for non-exposed NetBox areas such as custom fields, tags, config contexts, and user management, and there are no bulk operations, but core DCIM/IPAM/circuit/inventory workflows are supported end-to-end.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources