fios-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIOS_MCP_POLICY | No | Path to the policy.toml file holding the DNS allowlist, undeletable entries, and whether DMZ is allowed. Without one, DNS changes and DMZ are refused. | ~/.config/fios-mcp/policy.toml |
| FIOS_ROUTER_PIN | No | Path to the pinned router certificate PEM file. | ~/.config/fios-mcp/router.pem |
| FIOS_ROUTER_URL | No | URL of the router's local web interface. | https://192.168.1.1 |
| FIOS_ROUTER_PASSWORD | No | The router's admin password, supplied directly as an environment variable. FIOS_ROUTER_PASSWORD_FILE is preferred. | |
| FIOS_ROUTER_PASSWORD_FILE | No | Path to a file containing the router's admin password. File is preferred over FIOS_ROUTER_PASSWORD; must be chmod 600. | |
| FIOS_MCP_ALLOW_UNVERIFIED_FIRMWARE | No | When set, allows writes on firmware versions that have not been verified (by default writes are refused on unverified firmware). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Manages a Verizon Fios CR1000A router over its local web interface. Changes are two-phase: call a write tool without confirm to get a preview and state_etag, show the preview to the user, then call again with confirm=true and expected_etag. Never confirm a change the user has not seen. Wi-Fi keys and passwords are always redacted. On this router DHCP reservations in .100-.150 are reserved for Verizon devices and are refused. Wi-Fi changes make the router restart Wi-Fi and take 1-2 minutes to return. Moving the LAN (set_lan_settings) ends the session: tell the user the new address to reconnect to.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| router_statusC | Model, firmware, WAN address and DNS in use, LAN address. |
| router_firmwareB | Firmware version/date and whether this tool has been verified against it. |
| router_diagnosticsB | Connection, session and policy state of this MCP server (never secrets). |
| pingA | Ping an IPv4 address from the router itself (1-20 packets). |
| read_router_pageA | Raw (redacted) contents of one router page, for settings without a dedicated tool. Pages: see the fios://pages resource. |
| get_policyC | The owner's policy.toml guard-rails as loaded. |
| list_connected_devicesB | Devices the router knows, with MAC, IP, hostname and whether they are active. |
| list_dhcp_leasesA | Current DHCP leases (hostname, IP, MAC, seconds left). |
| list_arp_tableC | The router's ARP table. |
| get_wifi_summaryB | Physical radios per band, mesh state, and the primary/guest/IoT networks (SSID, on/off, security). Never includes keys. |
| set_wifi_radioA | Turn a physical Wi-Fi radio on or off (e.g. when another access point serves Wi-Fi). Two-phase; the router restarts Wi-Fi, so confirming takes 1-2 minutes. |
| set_wifi_networkA | Change a Wi-Fi network: on/off, SSID, password (8-63 chars) and/or security. |
| list_blocked_devicesC | Devices blocked from the network. |
| block_deviceC | Block a device (by MAC) from the network. Two-phase. |
| unblock_deviceC | Unblock a previously blocked device. Two-phase. |
| list_port_forwardingC | Port forwarding rules with their ports, target and enabled state. |
| add_port_forwardingB | Forward external port(s) (e.g. ["443"] or ["1000-2000"]) to a LAN host. Two-phase. internal_port: only if different from the external port. replace=true updates an existing rule on the same port instead of refusing. |
| delete_port_forwardingC | Delete a port forward by name, or by external port (+ protocol). Two-phase. |
| set_port_forwarding_enabledB | Enable or disable a port forward without deleting it. Two-phase. |
| get_lan_settingsC | LAN address, mask, DHCP range and lease time. |
| list_dhcp_reservationsC | DHCP reservations (MAC -> fixed IP). |
| add_dhcp_reservationC | Reserve an IP for a MAC. Refuses .100-.150 (reserved for Verizon devices). Two-phase. |
| delete_dhcp_reservationC | Remove the reservation for a MAC. Two-phase. |
| list_static_routesB | Configured IPv4 static routes (max 20); optionally the router's live routing table. |
| add_static_routeC | Route a network (CIDR, e.g. 10.99.0.0/24) via a LAN gateway. Two-phase. |
| delete_static_routeC | Delete the static route to a network (CIDR). Two-phase. |
| get_dns_settingsA | WAN DNS (IPv4 mode/servers in use, and IPv6 DNS mode). LAN clients use the router. Warns when IPv6 DNS is automatic: that is a second path to the ISP's resolvers. |
| set_dns_settingsB | Set WAN DNS. Manual servers must be in policy.toml's allowlist. Two-phase. |
| get_firewall_settingsC | Firewall security levels (IPv4/IPv6). |
| get_remote_admin_settingsC | Whether remote (WAN-side) administration and WAN ping/traceroute replies are enabled. |
| get_dmz_settingsC | DMZ host settings. |
| set_dmzB | Enable (needs features.allow_dmz in policy.toml) or disable the DMZ host. Two-phase. |
| get_upnp_settingsC | Whether UPnP (devices opening ports themselves) is enabled. |
| set_upnpC | Enable or disable UPnP. Two-phase. |
| reboot_routerA | Reboot the router (~4 minutes of downtime). Without confirm, only previews. |
| set_lan_settingsA | Change the router's LAN address, mask and DHCP pool (needs features.allow_lan_change). The preview lists reservations, forwards, routes and DMZ entries the new subnet would strand. If the address changes the router moves and this session ends: the result gives the new URL; the MCP server must be restarted with FIOS_ROUTER_URL pointing there. Two-phase. |
| snapshot_configA | Save every readable setting to a local snapshot file (0600); returns its id. |
| list_snapshotsB | Ids of saved snapshots, oldest first. |
| diff_configC | Differences between two snapshots, or a snapshot and the live router ("live"). |
| check_desired_stateA | Compare the router to a desired-state TOML file; lists what is missing or different. |
| apply_desired_stateA | Apply a desired-state TOML file item by item (never removes extra entries). Without confirm, returns the plan. With confirm, applies each item through the same validation and read-back as the individual tools, stopping at the first failure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| pages | Router pages readable with read_router_page |
TDQS
Scored across 41 tools
Most tools map cleanly to a resource+action pair (get/set_dns_settings, add/delete/list_port_forwarding, block/unblock_device), and descriptions explicitly disambiguate close pairs like list_dhcp_leases vs list_dhcp_reservations. The only soft spots are the informational cluster (router_status, router_firmware, router_diagnostics, get_remote_admin_settings) and the catch-all read_router_page, which slightly overlap in intent.
Overwhelmingly consistent snake_case verb_noun convention with a predictable get_/set_/list_/add_/delete_/block_ scheme, plus a well-signaled 'two-phase' confirm semantic shared across mutators. Minor deviations are the noun-first router_status / router_firmware / router_diagnostics and the bare ping, which break the get_-prefix family.
41 tools is heavy, but the domain is genuinely broad (Wi-Fi, DHCP, routing, DNS, firewall/DMZ/UPnP, port forwarding, snapshots, desired-state). Several small single-purpose readers (get_firewall_settings, get_dmz_settings, get_upnp_settings, get_remote_admin_settings) could be consolidated into one security-settings tool, which is why this sits at borderline rather than well-scoped.
Nearly every write surface has full lifecycle support: DHCP reservations, static routes, port forwarding (including enable/disable without delete), device blocking, Wi-Fi networks, plus snapshot/diff/desired-state workflows that cover bulk and audit use cases. Gaps are limited: get_remote_admin_settings and get_firewall_settings have no setters, and the guard-railed policy likely makes those deliberately read-only.