opn-mcp
Related Servers
Alternatives to opn-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to manage OPNsense firewall, interfaces, DHCP, DNS, routes, and services via natural language through 42 MCP tools.1MIT
- AlicenseBqualityBmaintenanceEnables AI clients to inspect OPNsense 26.7+ firewall state and, with policy and a separate write-capable API user, plan, approve, apply, verify, and automatically revert firewall rule and alias changes under hash-chained auditing.21MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language control of a pfSense firewall from Claude Desktop, Claude Code, or any MCP client, covering firewall rules, NAT, VPNs, DNS, DHCP, interfaces, packages, and diagnostics across 332 API-verified tools. Every change passes through safety guardrails with explicit confirmation, rate limiting, and captured config revisions for rollback.-
- 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.-
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage and configure pfSense routers through the pfSense REST API, offering 240 tools across 17 modules with safety features like confirm gates, config backups, and read-only mode.-
TDQS
Scored across 14 tools
Most tools have clear, distinct purposes: discovery (search/describe), the generic caller (opn_api), convenience wrappers (opn_items/opn_settings), and domain-specific helpers (ping, neighbors, firewall_log, overview, service, config tools). The main soft overlap is opn_api vs opn_items vs opn_settings, since all can write to model controllers, but descriptions explain the layering (generic escape hatch vs item-level vs whole-model).
All tools share a consistent opn_ snake_case prefix, which is readable and predictable. The verb/noun mix (opn_api_search, opn_config_revert vs opn_items, opn_overview, opn_service) is slightly inconsistent but each name still signals its role clearly.
14 tools is well within the ideal 3-15 range and each one earns its place: discovery, generic call, item/settings helpers, and targeted diagnostics/management tools. Nothing is redundant filler, and the count fits a broad OPNsense management surface.
The surface covers the full lifecycle well: discovery, read/write via opn_api/opn_items/opn_settings, apply/confirm/revert-now for firewall safety, config history/restore, plus diagnostics (ping, neighbors, log, overview, services). The generic opn_api acts as a catch-all for any gap, so coverage is strong, with only minor friction from needing controller/item knowledge to use the wrappers.