iptime-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPTIME_ROUTERS | No | JSON array of router profiles for multi-router configuration. Use username_env and password_env to reference environment variable names containing credentials. The referenced credential environment variables must also be set. | |
| IPTIME_ROUTER_ID | No | Profile name exposed as router_id. | default |
| IPTIME_ROUTER_URL | No | Router base URL using http or https. Required for single-router configuration. | |
| IPTIME_TIMEOUT_MS | No | Request timeout in milliseconds, clamped to 1000-60000. | 12000 |
| IPTIME_ROUTER_PASSWORD | No | Router administrator password. Required for login in single-router configuration. | |
| IPTIME_ROUTER_USERNAME | No | Router administrator username. Required for login in single-router configuration. | |
| IPTIME_TLS_FINGERPRINT | No | SHA-256 certificate fingerprint, with or without colons, checked in addition to normal TLS validation. | |
| IPTIME_ALLOW_INSECURE_REMOTE_HTTP | No | Allows plain HTTP when the hostname resolves to a public address. Set to 'true' to enable. | 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| iptime_statusA | Detect the router interface, authenticate if configured, and read product/system status. |
| iptime_loginA | Authenticate using credentials from the MCP environment. Credentials are never accepted as tool arguments. |
| iptime_logoutA | End the router admin session. |
| iptime_capabilitiesA | Discover which catalogued operations this model and firmware actually expose. |
| iptime_list_operationsA | List the fixed, auditable operation catalog. This does not contact the router. |
| iptime_readA | Run a read-only operation from iptime_list_operations. |
| iptime_backup_configB | Download the current router configuration to a new local .config file. Existing files are never overwritten. |
| iptime_plan_changeA | Create an expiring immutable plan for a router change. No setting is changed by this tool. |
| iptime_plan_firmware_upgradeA | Hash a local firmware file and create a critical-risk upgrade plan. No upload occurs yet. |
| iptime_plan_config_restoreB | Hash a local ipTIME configuration backup and create a critical-risk restore plan. |
| iptime_apply_changeA | Apply exactly one pending plan after its confirmation text is repeated verbatim. |
| iptime_cancel_changeB | Cancel a pending change plan. |
| iptime_list_plansB | List plans and their current state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| configuration | Configured router profiles with all credentials omitted |
| operation-catalog | Fixed router operation catalog and risk classification |
TDQS
Scored across 13 tools
Most tools target distinct actions, but iptime_status and iptime_read overlap slightly as both can retrieve router state, and iptime_capabilities vs iptime_list_operations could be confused by an agent looking for available operations. The descriptions clarify the differences enough that the set is mostly unambiguous.
The iptime_ prefix and verb-oriented names like list_*, apply_change, and cancel_change form a clear pattern. The main deviations are noun-style commands (iptime_status, iptime_capabilities) and compound plan_* names, but they are still readable and predictable.
Thirteen tools is well within the ideal range for a router management server, and each tool covers a distinct part of the workflow: session, discovery, read-only inspection, backup, planning, and safe application of changes. No tool feels redundant or missing.
The set covers session management, read-only inspection, backup, firmware/config-restore planning, and the apply/cancel workflow, which is a complete core lifecycle. Minor gaps exist such as no dedicated way to inspect a plan's detailed parameters or perform simple router actions like reboot, though these can be worked around via the general plan/read mechanisms.