firewalla-mcp
Related Servers
Alternatives to firewalla-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants and MCP clients with API access to manage Firewalla MSP resources including boxes, devices, alarms, rules, flows, and target lists.7 npmGPL 3.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with Firewalla network security devices for network monitoring, device management, traffic analysis, and security rule configuration through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude Desktop, Claude Code, and other MCP clients to manage a pfSense firewall through natural language — handling firewall rules, aliases, NAT, VPNs, routing, DNS, DHCP, certificates, users, services, logs, traffic shaping, and diagnostics across 332 API-verified tools. Every destructive change is guarded by confirmation prompts, rate limits, config-revision backup for rollback, and audit logging.-
- FlicenseNot gradedqualityAmaintenanceEnables managing a pfSense firewall in plain English from Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, routing, DNS, DHCP, certificates, and diagnostics across 332 wire-format-verified tools. Destructive changes pass through layered safety guardrails with explicit confirmation, rate limiting, config-revision backup and rollback, and secrets-redacted logging.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language control of pfSense firewalls from Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPN, DNS, DHCP, routing, certificates, users, and diagnostics through 332 wire-format-verified REST API tools. Destructive changes are gated behind explicit confirmation, rate limits, config-revision backups, and audit logging so an AI can safely diagnose and reconfigure a production firewall.-
- FlicenseNot gradedqualityAmaintenanceConnects Claude Desktop, Claude Code, or any MCP client to a pfSense firewall so users can query, diagnose, and change firewall rules, NAT, VPNs, DNS, DHCP, certificates, and other subsystems in natural language. Every destructive action is gated by confirmation prompts, rate limits, input validation, and config-revision rollback points, with tool request formats verified against the pfSense REST API.-
TDQS
Scored across 19 tools
Each tool targets a distinct resource or action. Tools for boxes, alarms, rules, target lists, flows, and devices are clearly separated with no overlapping purposes.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_rule, list_alarms, delete_target_list). No mixing of styles or vague verbs.
19 tools is on the higher end but still reasonable for comprehensive firewall management covering multiple resource types (boxes, alarms, rules, target lists, flows, devices). Each tool serves a distinct purpose.
CRUD coverage is mostly present for target lists (create, read, update, delete) and alarms (read, delete), but rules lack an update operation despite having pause/resume. Devices and flows are read-only, which is acceptable but leaves gaps for rule editing.