Skip to main content
Glama
jseifeddine

NetBox MCP Server

by jseifeddine

netbox_get_objects

Retrieve network infrastructure data from NetBox by specifying object types and applying filters to query devices, IP addresses, sites, and other network components.

Instructions

Get objects from NetBox based on their type and filters Args: object_type: String representing the NetBox object type (e.g. "devices", "ip-addresses") filters: dict of filters to apply to the API call based on the NetBox API filtering options

Valid object_type values:

DCIM (Device and Infrastructure):

  • cables

  • console-ports

  • console-server-ports

  • devices

  • device-bays

  • device-roles

  • device-types

  • front-ports

  • interfaces

  • inventory-items

  • locations

  • manufacturers

  • modules

  • module-bays

  • module-types

  • platforms

  • power-feeds

  • power-outlets

  • power-panels

  • power-ports

  • racks

  • rack-reservations

  • rack-roles

  • regions

  • sites

  • site-groups

  • virtual-chassis

IPAM (IP Address Management):

  • asns

  • asn-ranges

  • aggregates

  • fhrp-groups

  • ip-addresses

  • ip-ranges

  • prefixes

  • rirs

  • roles

  • route-targets

  • services

  • vlans

  • vlan-groups

  • vrfs

Circuits:

  • circuits

  • circuit-types

  • circuit-terminations

  • providers

  • provider-networks

Virtualization:

  • clusters

  • cluster-groups

  • cluster-types

  • virtual-machines

  • vm-interfaces

Tenancy:

  • tenants

  • tenant-groups

  • contacts

  • contact-groups

  • contact-roles

VPN:

  • ike-policies

  • ike-proposals

  • ipsec-policies

  • ipsec-profiles

  • ipsec-proposals

  • l2vpns

  • tunnels

  • tunnel-groups

Wireless:

  • wireless-lans

  • wireless-lan-groups

  • wireless-links

See NetBox API documentation for filtering options for each object type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
filtersYes

Implementation Reference

  • The primary handler function for the 'netbox_get_objects' MCP tool. It validates the object_type against the predefined mapping, constructs the NetBox API endpoint, and retrieves objects using the provided filters.
    @mcp.tool()
    def netbox_get_objects(object_type: str, filters: dict):
        """
        Get objects from NetBox based on their type and filters
        Args:
            object_type: String representing the NetBox object type (e.g. "devices", "ip-addresses")
            filters: dict of filters to apply to the API call based on the NetBox API filtering options
        
        Valid object_type values:
        
        DCIM (Device and Infrastructure):
        - cables
        - console-ports
        - console-server-ports  
        - devices
        - device-bays
        - device-roles
        - device-types
        - front-ports
        - interfaces
        - inventory-items
        - locations
        - manufacturers
        - modules
        - module-bays
        - module-types
        - platforms
        - power-feeds
        - power-outlets
        - power-panels
        - power-ports
        - racks
        - rack-reservations
        - rack-roles
        - regions
        - sites
        - site-groups
        - virtual-chassis
        
        IPAM (IP Address Management):
        - asns
        - asn-ranges
        - aggregates 
        - fhrp-groups
        - ip-addresses
        - ip-ranges
        - prefixes
        - rirs
        - roles
        - route-targets
        - services
        - vlans
        - vlan-groups
        - vrfs
        
        Circuits:
        - circuits
        - circuit-types
        - circuit-terminations
        - providers
        - provider-networks
        
        Virtualization:
        - clusters
        - cluster-groups
        - cluster-types
        - virtual-machines
        - vm-interfaces
        
        Tenancy:
        - tenants
        - tenant-groups
        - contacts
        - contact-groups
        - contact-roles
        
        VPN:
        - ike-policies
        - ike-proposals
        - ipsec-policies
        - ipsec-profiles
        - ipsec-proposals
        - l2vpns
        - tunnels
        - tunnel-groups
        
        Wireless:
        - wireless-lans
        - wireless-lan-groups
        - wireless-links
        
        See NetBox API documentation for filtering options for each object type.
        """
        # Validate object_type exists in mapping
        if object_type not in NETBOX_OBJECT_TYPES:
            valid_types = "\n".join(f"- {t}" for t in sorted(NETBOX_OBJECT_TYPES.keys()))
            raise ValueError(f"Invalid object_type. Must be one of:\n{valid_types}")
            
        # Get API endpoint from mapping
        endpoint = NETBOX_OBJECT_TYPES[object_type]
            
        # Make API call
        return netbox.get(endpoint, params=filters)
  • Dictionary mapping friendly object_type names to NetBox REST API endpoints, used for validation and endpoint resolution in the handler.
    # Mapping of simple object names to API endpoints
    NETBOX_OBJECT_TYPES = {
        # DCIM (Device and Infrastructure)
        "cables": "dcim/cables",
        "console-ports": "dcim/console-ports", 
        "console-server-ports": "dcim/console-server-ports",
        "devices": "dcim/devices",
        "device-bays": "dcim/device-bays",
        "device-roles": "dcim/device-roles",
        "device-types": "dcim/device-types",
        "front-ports": "dcim/front-ports",
        "interfaces": "dcim/interfaces",
        "inventory-items": "dcim/inventory-items",
        "locations": "dcim/locations",
        "manufacturers": "dcim/manufacturers",
        "modules": "dcim/modules",
        "module-bays": "dcim/module-bays",
        "module-types": "dcim/module-types",
        "platforms": "dcim/platforms",
        "power-feeds": "dcim/power-feeds",
        "power-outlets": "dcim/power-outlets",
        "power-panels": "dcim/power-panels",
        "power-ports": "dcim/power-ports",
        "racks": "dcim/racks",
        "rack-reservations": "dcim/rack-reservations",
        "rack-roles": "dcim/rack-roles",
        "regions": "dcim/regions",
        "sites": "dcim/sites",
        "site-groups": "dcim/site-groups",
        "virtual-chassis": "dcim/virtual-chassis",
        
        # IPAM (IP Address Management)
        "asns": "ipam/asns",
        "asn-ranges": "ipam/asn-ranges", 
        "aggregates": "ipam/aggregates",
        "fhrp-groups": "ipam/fhrp-groups",
        "ip-addresses": "ipam/ip-addresses",
        "ip-ranges": "ipam/ip-ranges",
        "prefixes": "ipam/prefixes",
        "rirs": "ipam/rirs",
        "roles": "ipam/roles",
        "route-targets": "ipam/route-targets",
        "services": "ipam/services",
        "vlans": "ipam/vlans",
        "vlan-groups": "ipam/vlan-groups",
        "vrfs": "ipam/vrfs",
        
        # Circuits
        "circuits": "circuits/circuits",
        "circuit-types": "circuits/circuit-types",
        "circuit-terminations": "circuits/circuit-terminations",
        "providers": "circuits/providers",
        "provider-networks": "circuits/provider-networks",
        
        # Virtualization
        "clusters": "virtualization/clusters",
        "cluster-groups": "virtualization/cluster-groups",
        "cluster-types": "virtualization/cluster-types",
        "virtual-machines": "virtualization/virtual-machines",
        "vm-interfaces": "virtualization/interfaces",
        
        # Tenancy
        "tenants": "tenancy/tenants",
        "tenant-groups": "tenancy/tenant-groups",
        "contacts": "tenancy/contacts",
        "contact-groups": "tenancy/contact-groups",
        "contact-roles": "tenancy/contact-roles",
        
        # VPN
        "ike-policies": "vpn/ike-policies",
        "ike-proposals": "vpn/ike-proposals",
        "ipsec-policies": "vpn/ipsec-policies",
        "ipsec-profiles": "vpn/ipsec-profiles",
        "ipsec-proposals": "vpn/ipsec-proposals",
        "l2vpns": "vpn/l2vpns",
        "tunnels": "vpn/tunnels",
        "tunnel-groups": "vpn/tunnel-groups",
        
        # Wireless
        "wireless-lans": "wireless/wireless-lans",
        "wireless-lan-groups": "wireless/wireless-lan-groups",
        "wireless-links": "wireless/wireless-links",
    
        # Extras
        "config-contexts": "extras/config-contexts",
        "custom-fields": "extras/custom-fields",
        "export-templates": "extras/export-templates",
        "image-attachments": "extras/image-attachments",
        "jobs": "extras/jobs",
        "saved-filters": "extras/saved-filters",
        "scripts": "extras/scripts",
        "tags": "extras/tags",
        "webhooks": "extras/webhooks",
    }
  • JSON schema definition for the netbox_get_objects tool used by the LLM client for tool calling.
    {
        "type": "function",
        "function": {
            "name": "netbox_get_objects",
            "description": "Get objects from NetBox based on their type and filters. Use this to retrieve devices, sites, IP addresses, VLANs, etc.",
            "parameters": {
                "type": "object",
                "properties": {
                    "object_type": {
                        "type": "string",
                        "description": "Type of NetBox object (e.g., 'devices', 'ip-addresses', 'sites', 'vlans', 'interfaces', 'racks', 'device-types', 'manufacturers', 'tenants', 'circuits', 'virtual-machines', 'prefixes', 'services')"
                    },
                    "filters": {
                        "type": "object",
                        "description": "Filters to apply to the API call. Common filters include 'site', 'status', 'limit', 'name', etc."
                    }
                },
                "required": ["object_type"]
            }
        }
  • server.py:103-103 (registration)
    FastMCP decorator that registers the netbox_get_objects function as an MCP tool.
    @mcp.tool()

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jseifeddine/netbox-mcp-chatbot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server