opnsense-guard-mcp
Related Servers
Alternatives to opnsense-guard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language management of OPNsense firewalls through AI clients, providing tools for firewall rules, system health, VPN monitoring, and more.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to manage OPNsense firewall, interfaces, DHCP, DNS, routes, and services via natural language through 42 MCP tools.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction and management of pfSense firewalls through Claude and other GenAI applications using the Model Context Protocol. It provides advanced tools for firewall rule configuration, interface management, and intelligent log analysis via a REST API integration.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language control of a pfSense firewall through Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, routing, DNS, DHCP, certificates, services, packages, and diagnostics. Every change passes through multi-layer safety guardrails with confirmation requirements, rate limiting, config revision backups for rollback, and audit logging.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language management of pfSense firewalls through MCP clients, covering firewall rules, VPNs, DNS, DHCP, diagnostics, configuration backup, and safety guardrails for destructive changes. It supports wire-format-verified operations across major pfSense subsystems with confirmation, rate limits, and rollback guidance.-
- 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.-
TDQS
Scored across 21 tools
Most tools target clearly distinct resources (suricata_status/settings/alert_status, firewall_rules/rule_get/log/states are well separated). Some softer overlap exists between posture_check and security_audit (both health/security snapshots) and among system_status/system_information/system_resources, but descriptions give enough signals to choose correctly.
All names are snake_case with predictable domain prefixes (system_, service_, suricata_, firewall_, dhcp_) and readable verb_noun forms for actions (posture_check, policy_show, security_audit). A few bare nouns (interfaces, arp_table, routing_table) deviate slightly but remain clear.
21 tools is on the heavy side for a read-only guard server; the suricata and system clusters each add several closely related tools. Every tool does earn a purpose, but the surface sits at the borderline of 'feels heavy'.
For a deliberately read-only server it covers system, services, IDS, firewall rules/aliases/logs/states, logs, interfaces, ARP, routing and DHCP well, with raw_get as an escape hatch for gaps. The notable gap is that policy_show references allowed changes but no mutation tools exist, which may confuse agents expecting lifecycle operations.