Skip to main content
Glama
ghbalf

mcp-fritzbox

by ghbalf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-fritzbox

No user-submitted related servers found.

    Related Servers

    • Device MCP Server

      akshitsinha
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for seamless integration with peripheral devices connected to your computer. Control, monitor, and manage hardware devices through a unified API.
      5
      MIT

    • flamerobin-mcp-server

      Michael2150
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for Firebird databases intended for local use. It reads connection details from FlameRobin's fr_databases.conf so no extra configuration is needed — if you have FlameRobin set up with your Firebird databases, this server works out of the box.
      29
      2
      MIT

    • mcp-tahoma

      pierresouchay
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for controlling Somfy TaHoma devices locally via the box's API, without cloud dependency.
      -

    • keenetic-mcp

      st412m
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Keenetic routers that runs on the router itself via Entware: clients, DHCP, Wi-Fi, VPN, logs, port forwarding and DNS records, with dry-run by default on every write. A background watcher calls out from the router when a log or config rule matches.
      49
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: listing devices, setting thermostats, toggling switches, retrieving stats, system info, WAN status, bandwidth, guest WiFi, logs, and reconnect. No two tools overlap in purpose; even get_device_stats and get_device_log are clearly differentiated as statistics vs. log entries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with imperative verbs (list, set, toggle, get, reconnect). No mixed conventions like camelCase or vague verbs, making the set predictable and easy to navigate.

    Tool Count5/5

    With 10 tools, the server is well-scoped for managing a FRITZ!Box. It covers both smart home device control (thermostats, switches) and network administration (WAN, WiFi, logs, connectivity) without unnecessary bloat or missing essential operations.

    Completeness4/5

    The tool surface covers the core lifecycle for both domains: listing, controlling, and retrieving information. Minor gaps exist, such as no explicit 'get current state' for thermostats/switches (though list_devices and stats may cover this) and no advanced configuration options like firmware updates, but these are not critical for typical usage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources