fritz-mesh-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRITZ_MASTER_HOST | Yes | Hostname or address of the FRITZ!Box mesh master | |
| FRITZ_MASTER_USER | Yes | Username for the FRITZ!Box mesh master; the user needs settings permission | |
| FRITZ_MASTER_PASSWORD | Yes | Password for the FRITZ!Box mesh master | |
| FRITZ_REPEATER_1_HOST | No | Optional hostname or address of an adopted repeater | |
| FRITZ_REPEATER_1_USER | No | Optional username for an adopted repeater | |
| FRITZ_REPEATER_1_PASSWORD | No | Optional password for an adopted repeater |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fritz_mesh_statusA | Read the master and both repeaters: adoption, SSID, steering, channel mode, and power. |
| fritz_list_devicesA | List devices known to the mesh master, including band, parent, and IP. |
| fritz_get_deviceA | Read one device. uid is the FRITZ id, for example landevice1. |
| fritz_get_radioA | Read band steering, channel mode, channels, and transmit power. host defaults to the master. |
| fritz_set_band_steeringB | Turn client band steering on or off on the master, keeping channel mode and power as they are. |
| fritz_set_channel_modeC | Set channel selection to auto or manual. Manual may include a 2.4 GHz and a 5 GHz channel. |
| fritz_set_transmit_powerC | Set transmit power. 1 is 100%, then 50%, 25%, 12%, and 6%. |
| fritz_set_coexistenceA | Turn 2.4 GHz Wi-Fi coexistence on or off without changing steering, channel, or power. |
| fritz_set_backhaul_steeringB | Turn mesh backhaul steering on or off. This is separate from client band steering. |
| fritz_reserve_ipv4C | Reserve or release the IPv4 address of one device. Pass ip to pin a specific address. |
| fritz_connection_statusC | WAN state from TR-064: model, external address, uptime, and whether an update is offered. |
| fritz_wifi_networksC | SSIDs, channels, and bands from TR-064. Wi-Fi passwords are not included. |
| fritz_lan_dhcpB | DHCP range, mask, and DNS. Per-device reservations use fritz_reserve_ipv4. |
| fritz_system_logC | Recent system log lines from the master, or from host. |
| fritz_port_forwardsD | Active IPv4 port-forwarding rules. |
| fritz_set_guest_wifiB | Enable or disable the guest Wi-Fi network on the master. |
| fritz_set_wan_accessB | Block or restore one device's internet access by IPv4 address. |
| fritz_set_upnpB | Enable or disable UPnP port forwarding. The media server stays off. |
| fritz_wake_on_lanC | Ask the master to send a Wake-on-LAN packet. |
| fritz_smart_home_devicesC | DECT smart-home devices the master can see. |
| fritz_set_smart_home_switchC | Switch a smart-home actuator by its AIN. |
| fritz_rebootA | Reboot the master. The network drops for about two minutes. |
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 22 tools
Most tools map to a distinct resource+action, and the descriptions proactively disambiguate the risky pairs (band steering vs backhaul steering, reserve_ipv4 vs lan_dhcp, mesh_status vs get_radio). There is still some read overlap: fritz_mesh_status and fritz_get_radio both surface channel mode/power, and fritz_wifi_networks vs fritz_connection_status both touch WAN/Wi-Fi state, so an agent may occasionally pick the broader one.
All tools share a fritz_ prefix and snake_case, and mutating tools consistently use fritz_set_*/fritz_reserve_*/fritz_reboot. Read tools are mixed, however: some use get_/list_ (fritz_get_device, fritz_list_devices) while others are bare nouns (fritz_wifi_networks, fritz_lan_dhcp, fritz_system_log, fritz_port_forwards), which slightly breaks the pattern predictability.
22 tools is on the heavy side but the domain is genuinely broad (mesh/radio, devices, WAN, LAN/DHCP, firewall, WoL, smart home, logs), and each tool corresponds to a real router capability rather than filler. It is close to the point where a grouped read tool would be preferable, but nothing feels redundant.
Read coverage is strong (status, devices, radio, WAN, Wi-Fi, DHCP, logs, port forwards, smart home) and most config knobs have a setter, including steering, channel, power, guest Wi-Fi, WAN blocking, UPnP, and IP reservation. The main gaps are write-side: port forwarding is list-only (no create/delete rule), and there is no way to change SSIDs/passwords or manage smart-home setpoints beyond a binary switch.