Skip to main content
Glama
amittell

firewalla-mcp-server

Related Servers

Alternatives to firewalla-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with Firewalla network security devices for network monitoring, device management, traffic analysis, and security rule configuration through MCP tools.
      -
    • A
      license
      B
      quality
      A
      maintenance
      Exposes the Firewalla MSP API as tools for Claude Code and other MCP clients, enabling natural-language management of Firewalla boxes, alarms, rules, devices, flows, target lists, and trends with full read/write capabilities.
      19
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides real-time access to Firewalla firewall data through 28 specialized tools for network monitoring, security analysis, bandwidth tracking, and firewall rule management. Enables users to query security alerts, analyze network flows, monitor device status, and manage firewall configurations through natural language.
      516 npm
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      A secure MCP server for managing OPNsense firewalls through AI assistants. Provides 81 tools across system, firewall, network, DNS, DHCP, VPN, HAProxy, services, diagnostics, and security domains.
      81
      232 PyPI
      21
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI-powered security operations through natural language, managing endpoint security, email threats, firewall policy, and more across multiple Sophos tenants with 334 tools, designed for MSP/MSSP teams.
      100
      41 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 28 tools

    Disambiguation3/5

    Several tools overlap in purpose: get_offline_devices and get_device_status both read device lists and report online/offline status; get_flow_data, search_flows, and get_recent_flow_activity all query flows with different scopes; get_network_rules and search_rules both retrieve rules. Descriptions help distinguish them, but the boundaries are not always obvious.

    Naming Consistency4/5

    Most tools follow a consistent get_/search_/create_/update_/delete_/pause_/resume_ verb pattern with clear noun objects. Minor deviations like get_network_rules_summary and get_specific_target_list vs get_specific_alarm are acceptable, but the mix of get_ and search_ for similar resources (flows, alarms, rules) creates slight inconsistency.

    Tool Count3/5

    28 tools is on the heavy side for a single server, though the domain (Firewalla MSP API) is broad with devices, alarms, flows, rules, target lists, and statistics. The count is borderline: many tools are convenience wrappers or variations on the same resource, which could be consolidated.

    Completeness4/5

    The tool set covers the main Firewalla MSP resources well: devices, alarms, flows, rules, target lists, and statistics. Minor gaps exist (e.g., no create/update/delete for rules or alarms, no device management actions), but the core read and search operations are comprehensive.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow