Firewalla-mcp-server

Firewalla MCP Server is a Model Context Protocol (MCP) server that connects your Firewalla firewall to any compatible AI client.

  • AI
  • Network Services
Firewalla MCP Server is a Model Context Protocol (MCP) server that connects your Firewalla firewall to any compatible AI client. It exposes 24 read-only tools for real-time network monitoring, security alert review, and firewall rule management, plus 11 opt-in write tools. It's for self-hosters who want natural-language access to their Firewalla data from AI tools; write access is disabled by default so your device stays untouched unless you enable it.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
88last commit 9 days ago
Popular
3343 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
2032 GB minimum RAM, runs on ARM
Security check
90no serious findings, tests
GitHub stars
43
Open issues
3
Last commit
2026-11-11
Latest release
v2.1.1
License
MIT
Activity
declining

Checked yesterday - source: GitHub (amittell/firewalla-mcp-server)

Resources & Compatibility

Minimum requirements: 32 GB RAM, 8 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Firewalla MSP account with API access required The server reads your data through the Firewalla MSP API, so you must have a Firewalla MSP account with API access enabled before it can connect. Write tools stay disabled unless you set FIREWALLA_ENABLE_WRITE_TOOLS=true. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Firewalla-mcp-server change my Firewalla configuration by default?

No. The 11 write tools stay off unless you set FIREWALLA_ENABLE_WRITE_TOOLS=true, so by default it only exposes read-only monitoring and review tools.

Does the server need direct access to my Firewalla device?

It reads your data through the Firewalla MSP API. You still need a Firewalla MSP account with API access, and the device must be online and connected.

Why does npm show an EBADENGINE warning on Node 18, 20, or 22?

The warning comes from geoip-lite 2.x, which declares Node 24 for its database update script. The server's geoip lookups still run on Node 18 and later, and CI tests Node 18, 20, 22, and 24.

How can I connect Firewalla-mcp-server to Open WebUI?

Use mcpo or a native MCP connection over HTTP.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads