snmp-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snmp_getA | Fetch one or more OIDs in a single SNMP GET-Request. Accepts numeric (e.g. 1.3.6.1.2.1.1.5.0) and a small set of symbolic forms (e.g. SNMPv2-MIB::sysName.0). Returns a dict keyed by OID with {value, type} per varbind. |
| snmp_walkA | Walk an OID subtree via GETNEXT chain. Terminates on endOfMibView or when the next OID leaves the subtree. Returns a list of {oid, value, type} rows. |
| snmp_bulk_walkA | Walk an OID subtree via GETBULK (SNMPv2c+). Faster than snmp_walk for large tables; falls back to GETNEXT with a warning on v1 hosts. max_repetitions defaults to 25. |
| snmp_tableA | Walk and tabularize an SNMP table. Returns {table_oid, rows: [{index, : value, ...}, ...]}. Column-name mapping is best-effort: unknown columns are keyed by numeric OID. |
| system_infoB | Fetch the SNMPv2-MIB::system group (RFC 3418): sysDescr, sysObjectID, sysUpTime (centiseconds and seconds), sysContact, sysName, sysLocation, sysServices. |
| interfaces_listA | List network interfaces via IF-MIB (RFC 2863). Merges ifTable + ifXTable per ifIndex. HC counters (ifHCInOctets / ifHCOutOctets) are returned alongside 32-bit counters. ifSpeed saturation at ~4.29 Gbps is handled automatically — ifSpeed_bps falls back to ifHighSpeed*1e6 with ifSpeed_source='ifHighSpeed' and a warning. |
| host_resourcesA | HOST-RESOURCES-MIB (RFC 2790) summary: CPU load per core (hrProcessorLoad), memory (hrMemorySize + derived swap), uptime, process count, and storage table (filesystems + RAM + swap). Raises 'unsupported' if the agent does not implement the MIB at all (typical on bare network switches). |
| printer_statusC | PRINTER-MIB (RFC 3805) status: supplies (toner / ink / drum levels with percent computed when capacity is known), input trays, output bins, and active alerts. Works across HP, Brother, Canon, OKI, Epson, Lexmark. Sentinel values (-2 unknown, -3 not measured) are handled per RFC 3805. |
| device_detectA | Probe which standard MIBs a device implements. Issues 5 GETs (sysObjectID, sysDescr, ifNumber, hrSystemUptime, prtGeneralPrinterStatus.1.1) and reports a vendor hint (decoded from the sysObjectID enterprise number) plus a list of supported_mibs. Useful as a smoke test before calling heavier tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Tools are largely distinct, but snmp_walk and snmp_bulk_walk share the same purpose (walking an OID subtree) differing only in method, which could cause confusion. Additionally, snmp_table is a specialized walk. However, descriptions clarify the differences.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., device_detect, snmp_get, interfaces_list), making it easy for agents to predict and select the correct tool.
With 9 tools, the server covers core SNMP operations (get, walk, bulk walk, table) and common MIB groups (system, interfaces, host resources, printer). The count is well-balanced for its scope.
The tool set provides both low-level SNMP access and high-level summaries for common device types. It includes detection (device_detect), system info, interfaces, resources, and printer status. The only notable gap is lack of SNMP SET, but that aligns with the server's focus on read-only monitoring.