MCP Nautobot Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ip_addressesC | Retrieve IP addresses from Nautobot with filtering options |
| get_prefixesC | Retrieve network prefixes from Nautobot with filtering options |
| get_ip_address_by_idB | Retrieve a specific IP address by its Nautobot ID |
| search_ip_addressesB | Search IP addresses using a general query string |
| test_connectionB | Test the connection to the Nautobot API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ip-summary-report | Generate a comprehensive IP address summary report |
| network-utilization | Analyze network prefix utilization and capacity |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| IP Addresses | Nautobot IP address data with filtering capabilities |
| Network Prefixes | Nautobot network prefix data with filtering capabilities |
| Nautobot Connection Status | Current status of the Nautobot API connection |
TDQS
Scored across 5 tools
Most tools have distinct purposes: get_ip_address_by_id retrieves a specific IP, get_ip_addresses lists IPs with filters, get_prefixes handles prefixes, and test_connection is unique. However, get_ip_addresses and search_ip_addresses have some overlap, as both involve retrieving IP addresses, which could cause mild confusion about when to use each.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., get_ip_address_by_id, search_ip_addresses). The naming is predictable and readable across all five tools, with no deviations in style.
With 5 tools, the count is reasonable for a server focused on IP address and prefix management in Nautobot. It's slightly lean but covers core retrieval and testing operations without feeling bloated, though it could benefit from more actions like create or update tools.
The tool set is severely incomplete for managing IP addresses and prefixes in Nautobot. It only provides retrieval and search operations, with no tools for creating, updating, or deleting IP addresses or prefixes. This leaves significant gaps that will hinder agents from performing full lifecycle management.