Labsco
MCP SERVER

OPNsense MCP Server

by Pixelworlds ↗

Reach the whole OPNsense API through 24 dispatch tools — you pass a subsystem's method name and its params instead of hunting through hundreds of separate tool definitions.

Network, Endpoint & Fleet Management✓ Verified
Summary
A firewall's entire API fits in your context as 24 definitions instead of hundreds.

Because the method list stays out of the tool schema, adding this server costs a fixed and small amount of context no matter how much of OPNsense you end up using. The bill comes due at call time: the descriptions name only the first few methods per subsystem, so any other method name has to come from OPNsense's own API reference before you can invoke it.

What it is

A thin wrapper over the OPNsense API arranged as one tool per subsystem: 24 tools, each taking a method and params.

What you get
  • Firewall work on one dispatcher, including alias item add and delete and GeoIP alias reads
  • Interfaces and routing across three subsystems: interface, route and routing methods
  • Address assignment spread over DHCPv4, DHCPv6, DHCP relay, Kea and dnsmasq
  • VPN in all three flavours — IPsec, OpenVPN and WireGuard, one dispatcher each
  • Live state and monitoring: diagnostics from CPU usage streams to reverse DNS lookups, plus Monit service checks and syslog
  • Security and trust: IDS methods including alert queries, trust methods for certificate authorities, captive portal and authentication
  • Housekeeping through the core module, which covers backups, and the firmware module, which covers audit, changelog and check
Requirements

An OPNsense URL with an API key and secret, and npx on your PATH. Each call also needs the exact method name for its subsystem; the tool descriptions name the first five of each.

Setup effort

One command plus a key — npm install -g @richard-stovall/opnsense-mcp-server, then supply credentials