Skip to main content
Glama
David41186

netbox-mcp

by David41186
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NETBOX_URLNoURL of your NetBox instance. Defaults to https://demo.netbox.dev.https://demo.netbox.dev
NETBOX_TOKENYesAPI token from your NetBox user profile (Admin > API Tokens). Required for both reads and writes.
NETBOX_VERIFY_SSLNoSet to 'false' only if your instance uses a self-signed certificate.true
NETBOX_MCP_READ_ONLYNoSet to 'true' to disable all create/update/delete tools. Recommended until you are confident in the setup.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
netbox_list_endpointsA

List every supported NetBox 'app.endpoint' value, grouped by app, with a short description of what each endpoint represents. Call this first to discover which endpoint strings are valid for the other tools.

netbox_get_schemaA

Get field definitions for a NetBox endpoint (names, types, whether required/read-only, and valid choice values), via an authenticated OPTIONS request. Use this before creating or updating objects to see what fields are valid.

    Args:
        endpoint: An "app.endpoint" string, e.g. "dcim.devices". See
            netbox_list_endpoints for valid values.
netbox_list_objectsA

List/search objects at a NetBox endpoint.

    Args:
        endpoint: An "app.endpoint" string, e.g. "ipam.prefixes". See
            netbox_list_endpoints for valid values.
        filters: Optional field filters applied server-side, e.g.
            {"site": "ams1", "status": "active"}. Omit to list all objects.
        limit: Maximum number of objects to return (default 50, use 0 for
            no limit).
netbox_get_objectA

Get a single object from a NetBox endpoint by its numeric ID.

    Args:
        endpoint: An "app.endpoint" string, e.g. "dcim.devices".
        id: The object's numeric ID.
netbox_create_objectA

Create a new object at a NetBox endpoint. Disabled when the server is running in read-only mode.

    Args:
        endpoint: An "app.endpoint" string, e.g. "dcim.sites".
        data: Field values for the new object. Use netbox_get_schema to
            see required and valid fields first.
netbox_update_objectA

Partially update an existing object at a NetBox endpoint. Only the fields included in data are changed. Disabled when the server is running in read-only mode.

    Args:
        endpoint: An "app.endpoint" string, e.g. "dcim.devices".
        id: The object's numeric ID.
        data: Field values to change.
netbox_delete_objectA

Delete an object from a NetBox endpoint. This is permanent. Requires confirm=True to actually perform the deletion, and is disabled when the server is running in read-only mode.

    Args:
        endpoint: An "app.endpoint" string, e.g. "dcim.devices".
        id: The object's numeric ID.
        confirm: Must be explicitly set to true to perform the deletion.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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