OPNsense MCP Server
Related Servers
Alternatives to OPNsense MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for comprehensive OPNsense firewall management, enabling AI assistants to manage firewall rules, NAT, VLANs, and network diagnostics, plus execute SSH/CLI commands. Supports safety modes like read-only and dry-run for safe operation.MIT
- AlicenseNot gradedqualityDmaintenanceA modular MCP server that provides access to over 2,000 OPNsense firewall management methods through 88 specialized tools. It enables AI assistants to securely manage firewall rules, network interfaces, and system diagnostics using a type-safe TypeScript interface.96MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to manage OPNsense firewall, interfaces, DHCP, DNS, routes, and services via natural language through 42 MCP tools.1MIT
- AlicenseNot gradedqualityBmaintenanceManage a fleet of OPNsense firewalls from an AI agent, inside guardrails it can't drive around. MCP server for central management of OPNsense firewall fleets. 129 tools across devices, config sync, tasks, schedules, templates, backups and remote consoles - destructive actions confirmation-gated, MCP-issued tokens lifetime-bounded, backup and storage secrets excluded from the toolset entirely.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables AI agents to inspect and modify an OPNsense firewall via natural language, using a compact set of generic tools and a resource registry to cover 96 CRUD operations.17 npmAGPL 3.0
- AlicenseAqualityDmaintenanceEnables interaction with OPNsense firewalls through MCP tools for managing firewall rules, interfaces, DHCP leases, and system monitoring.26MIT
TDQS
Scored across 81 tools
Most tools are clearly separated by resource and action, and descriptions explicitly warn about MVC vs legacy firewall rules and backend-specific DHCP lease tools. A few areas remain confusable, especially the three DHCP lease listings, opn_set_dnsbl vs opn_update_dnsbl, and the various HAProxy reconfigure/configtest/status tools.
The opn_ prefix is used throughout and most names follow a predictable action_resource pattern such as opn_list_firewall_rules and opn_add_nat_rule. Minor deviations exist, including HAProxy's resource-first naming, alias singular/plural inconsistency, and opn_update_dnsbl meaning 'reload' rather than update configuration.
81 tools is an extreme number for a single MCP server and far beyond the typical 3-15 well-scoped range. While OPNsense is broad, this surface is large enough to make discovery and correct selection burdensome for an agent.
Core areas such as firewall rules, aliases, NAT, DNS overrides, DNSMasq ranges, DDNS, and HAProxy have substantial CRUD coverage, while several other areas are only partially covered. Static routes, services, cron jobs, ACME certificates, and most VPN configuration are read-only or status-only, leaving notable lifecycle gaps.