# kambriso/fritzbox-mcp-server [Health: Active]

**Category:** 🏠 Home Automation  
**Repository:** https://github.com/kambriso/fritzbox-mcp-server  
**GitHub Stars:** 18  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kambriso-fritzbox-mcp-server

## Description
Control AVM FRITZ!Box routers - manage devices, WiFi, network settings, parental controls, and schedule time-delayed actions

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "fritzbox-mcp-server": {
    "command": "npx",
    "args": ["-y","kambriso-fritzbox-mcp-server"]
  }
}
```

## Documentation

## What kambriso/fritzbox-mcp-server MCP server does

kambriso/fritzbox-mcp-server MCP server lets an MCP-compatible AI client query and manage an AVM FRITZ!Box router using natural-language requests. Its documented use cases include checking the external IP, connected devices, router uptime, internet speed, WiFi security, connection quality, line quality, error rates, and recent logs.

The server also supports device-oriented operations. An assistant can list online and offline devices, distinguish WiFi from Ethernet connections, identify unknown devices, inspect bandwidth use, and prioritize a device. Router configuration examples cover WiFi, guest WiFi, parental controls, and internet access restrictions.

Scheduled operations are another supported function. For example, a gaming console can be blocked after a delay, or internet access can be disabled during specified work hours. The README states that delayed actions can continue through the server’s CLI mode after the chat is closed.

## How it works

The executable runs on the user’s computer and communicates with the FRITZ!Box across the local network. An AI agent connects to the local process, which acts as the intermediary for router requests. The router does not need to be reachable from the public internet, and the setup does not require opening inbound ports or creating a cloud connection to the router.

FRITZ!Box credentials are stored locally in a `.env` file. The documented security model keeps those credentials on the computer running the server and returns results—such as device counts or uptime—to the AI agent instead of passing the credentials to it.

During setup, the server can discover FRITZ!Box devices with SSDP and identify the mesh master or gateway. The README also says that the server discovers router capabilities at runtime and is intended to work across FRITZ!Box models and firmware versions.

## Setup and configuration

Linux and macOS users can run the project’s installation script, which detects the operating system and CPU architecture, downloads a release, verifies SHA256 checksums, and installs the `fritz-mcp` binary under `~/.local/bin` by default. Releases are also provided as archives for Linux, macOS, and Windows.

Run `fritz-mcp --setup` for the interactive configuration flow. It discovers the router, asks for the host, username, password, and TLS preference, then writes the credentials to a `.env` file with permissions restricted to the current user.

The FRITZ!Box account must have permission to view and edit all FRITZ!Box settings. For Claude Desktop, add the executable’s absolute path as a local server command and restart the client after changing its configuration.

## Tools and capabilities

Documented capabilities include:

- Querying router status, uptime, external IP, speed, and connection health
- Listing connected, registered, unknown, WiFi, and Ethernet devices
- Reviewing bandwidth use, connection errors, logs, and disconnections
- Managing WiFi, guest WiFi, device priority, and parental controls
- Scheduling time-delayed access restrictions and other actions

## Limitations and notes

The router must be reachable from the computer running the server, and the configured FRITZ!Box user needs full settings access. If the MCP client cannot see the server, the README recommends checking the absolute executable path and restarting the client. Windows configuration paths require escaped backslashes. Because the server communicates with the router locally, it is intended for environments where the MCP client can launch a local stdio process.

_Full upstream README: https://allmcps.com/mcp/kambriso-fritzbox-mcp-server/readme_