Skip to main content
Glama
David41186

netbox-mcp

by David41186
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to netbox-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • nautobot-mcp

      shamalawy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Nautobot instances through schema-driven tools for CRUD operations, dependency planning, and GraphQL queries, efficiently handling large APIs without overwhelming agent context.
      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

    • Netdisco MCP

      omichelbraga
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with the Netdisco network management platform through its complete REST API, supporting device inspection, port queries, VLAN searches, and job management.
      MIT
    • 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
      231
      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

    A4.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: endpoint discovery, schema introspection, list/search, get by ID, and create/update/delete. The only potential overlap is list_objects vs get_object, but their descriptions make the collection-versus-single-object distinction unambiguous.

    Naming Consistency5/5

    All tools follow a consistent netbox_verb_noun pattern (e.g., netbox_list_objects, netbox_create_object, netbox_get_schema). The naming convention is uniform and predictable across the entire set.

    Tool Count5/5

    Seven tools is well-scoped for a generic NetBox CRUD interface. Each tool covers a distinct operation needed to interact with any NetBox endpoint without being redundant or overwhelming.

    Completeness5/5

    The toolset provides full lifecycle coverage for NetBox objects: discovery, schema inspection, listing/searching, retrieving, creating, updating, and deleting. The endpoint-driven design means these operations apply broadly across NetBox's many object types, so there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources