Skip to main content
Glama

fritz-mesh-mcp

stdio MCP for a FRITZ!Box mesh. It logs in with the current two-round PBKDF2 challenge and also accepts the older single-round and MD5 challenges. Writes go to the mesh master. Adopted repeaters are read so you can see that they still follow it.

Other public Fritz MCPs stop at TR-064, telephony, or a generic “post this web form” call. TR-064 does not expose client band steering, transmit power, or the “always assign this IPv4 address” flag. A partial post of the channel page is what clears channel mode and power. This server names those settings and, on every radio change, resubmits the current channel mode, channels, and power with the one field you are changing.

What the others do not name

This server

dimitree2k/fritzbox-mcp

ghbalf/mcp-fritzbox

kambriso/fritzbox-mcp-server

the78mole/fritzmoles-mcp

Several boxes, master plus adopted repeaters

yes

one box

one box

one box

telephony

Current PBKDF2 login

yes

yes

MD5 only

varies

TR-064

Client band steering

named tool

only via a raw page post

no

no

no

Channel mode and transmit power, saved with the other radio fields

yes

raw page post

no

no

no

Mesh backhaul steering

yes

no

no

no

no

Per-device IPv4 reservation

yes, /api/v0

no (TR-064 cannot)

no

no

no

WAN, Wi-Fi list, DHCP range, log, port forwards, guest Wi-Fi, UPnP, Wake-on-LAN, smart home, reboot

named tools

named tools, plus a generic action caller

partial

home automation

calls and answering machine

dimitree2k/fritzbox-mcp can reach settings this server does not wrap, because it will post any page and call any TR-064 action. That is a wider escape hatch, and it is the path that drops radio settings. This server does not include that escape hatch.

Related MCP server: mcp-fritzbox

Tools

Mesh and devices: fritz_mesh_status, fritz_list_devices, fritz_get_device.

Radio, master only: fritz_get_radio, fritz_set_band_steering, fritz_set_channel_mode, fritz_set_transmit_power (1 is 100%, then 50, 25, 12, and 6 percent), fritz_set_coexistence, fritz_set_backhaul_steering.

Addressing: fritz_reserve_ipv4, fritz_lan_dhcp.

Router: fritz_connection_status, fritz_wifi_networks, fritz_system_log, fritz_port_forwards, fritz_set_guest_wifi, fritz_set_wan_access, fritz_set_upnp, fritz_wake_on_lan, fritz_smart_home_devices, fritz_set_smart_home_switch, fritz_reboot.

Wi-Fi passwords are dropped from every reply.

Run

uv sync
export FRITZ_MASTER_HOST=fritz.box
export FRITZ_MASTER_USER=...
export FRITZ_MASTER_PASSWORD=...
# optional adopted repeaters
export FRITZ_REPEATER_1_HOST=repeater-1.local
export FRITZ_REPEATER_1_USER=...
export FRITZ_REPEATER_1_PASSWORD=...
uv run fritz-mesh-mcp

Cursor, or any other stdio client:

{
  "mcpServers": {
    "fritz-mesh": {
      "command": "uv",
      "args": ["run", "--directory", "/absolute/path/to/fritz-mesh-mcp", "fritz-mesh-mcp"]
    }
  }
}

The FRITZ!Box user needs the settings permission. TR-064 (port 49000) has to be reachable on the LAN. fritz_reboot takes the master offline for about two minutes.

Tests

uv run python -m unittest tests.test_client

The unit tests do not touch a router. A live check is logging in and reading fritz_get_radio before any write.

Available Tools

22 tools
fritz_connection_statusC

WAN state from TR-064: model, external address, uptime, and whether an update is offered.

Inputs: host.

fritz_get_deviceA

Read one device. uid is the FRITZ id, for example landevice1.

Inputs: uid (required).

fritz_get_radioA

Read band steering, channel mode, channels, and transmit power. host defaults to the master.

Inputs: host.

fritz_lan_dhcpB

DHCP range, mask, and DNS. Per-device reservations use fritz_reserve_ipv4.

Inputs: host.

fritz_list_devicesA

List devices known to the mesh master, including band, parent, and IP.

Inputs: no named parameters. Returns: result

fritz_mesh_statusA

Read the master and both repeaters: adoption, SSID, steering, channel mode, and power.

Inputs: no named parameters.

fritz_port_forwardsD

Active IPv4 port-forwarding rules.

Inputs: host. Returns: result

fritz_rebootA

Reboot the master. The network drops for about two minutes.

Inputs: no named parameters.

fritz_reserve_ipv4C

Reserve or release the IPv4 address of one device. Pass ip to pin a specific address.

Inputs: uid (required), ip, reserve.

fritz_set_backhaul_steeringB

Turn mesh backhaul steering on or off. This is separate from client band steering.

Inputs: enabled (required).

fritz_set_band_steeringB

Turn client band steering on or off on the master, keeping channel mode and power as they are.

Inputs: enabled (required).

fritz_set_channel_modeC

Set channel selection to auto or manual. Manual may include a 2.4 GHz and a 5 GHz channel.

Inputs: mode (required), channel_5, channel_24.

fritz_set_coexistenceA

Turn 2.4 GHz Wi-Fi coexistence on or off without changing steering, channel, or power.

Inputs: enabled (required).

fritz_set_guest_wifiB

Enable or disable the guest Wi-Fi network on the master.

Inputs: enabled (required).

fritz_set_smart_home_switchC

Switch a smart-home actuator by its AIN.

Inputs: on (required), ain (required).

fritz_set_transmit_powerC

Set transmit power. 1 is 100%, then 50%, 25%, 12%, and 6%.

Inputs: step (required).

fritz_set_upnpB

Enable or disable UPnP port forwarding. The media server stays off.

Inputs: enabled (required).

fritz_set_wan_accessB

Block or restore one device's internet access by IPv4 address.

Inputs: blocked (required), ip_address (required).

fritz_smart_home_devicesC

DECT smart-home devices the master can see.

Inputs: no named parameters. Returns: result

fritz_system_logC

Recent system log lines from the master, or from host.

Inputs: host, limit.

fritz_wake_on_lanC

Ask the master to send a Wake-on-LAN packet.

Inputs: mac_address (required).

fritz_wifi_networksC

SSIDs, channels, and bands from TR-064. Wi-Fi passwords are not included.

Inputs: host. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 22 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for interfacing with AVM FRITZ!Box routers. Control smart home devices, monitor network status, and administer your router through any MCP-compatible client.
      10
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and other MCP clients to inspect and manage a TP-Link router over stdio, including device lists, DHCP leases and reservations, Wi-Fi settings, firmware and IP status, mesh nodes, and safe raw endpoint requests with confirmation for writes and secret masking.
      16
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM clients to inspect and manage a TP-Link Deco mesh Wi-Fi network, covering mesh nodes, connected devices, SSIDs and radio settings, internet status, blocked clients, and DHCP address reservations. Runs entirely against the router on the local network without any cloud account.
      15
      54 PyPI
      MIT