OPNsense MCP Server
Manage OPNsense DNS, firewall, DHCP, routing, VLANs, and ACME from an MCP agent when you run your own edge firewall at home or for a small product.
Overview
OPNsense MCP Server is an Operate-phase MCP server that offers 72 tools to manage OPNsense DNS, firewall, DHCP, ACME, routing, VLANs, and more from an AI assistant.
What is this MCP server?
- 72 MCP tools for DNS, Firewall, DHCP, ACME, Routing, VLANs, and related OPNsense areas
- stdio via npx @itunified.io/mcp-opnsense (package version 2026.4.10-4)
- OPNSENSE_URL, OPNSENSE_API_KEY, OPNSENSE_API_SECRET, optional OPNSENSE_VERIFY_SSL for self-signed certs
- GitHub source at itunified-io/mcp-opnsense for self-hosted network operators
- 72 tools documented in server description
- Server version 2026.4.10; npm package version 2026.4.10-4
- Four documented env vars including optional OPNSENSE_VERIFY_SSL
Community signal: 1 GitHub stars.
What problem does it solve?
Your network runs on OPNsense but every DNS or firewall tweak means logging into the UI or scripting the API while your agent stays blind.
Who is it for?
Self-hosters and indie operators with an OPNsense appliance who want MCP-assisted network and certificate management.
Skip if: Teams on cloud-only networking, or anyone unwilling to scope API keys and review firewall changes before applying them.
What do I get? / Deliverables
With URL and API credentials configured, your agent can call OPNsense MCP tools to inspect and change router services you authorize.
- Agent-driven OPNsense operations across DNS, firewall, DHCP, ACME, routing, and VLAN tooling
- stdio MCP bridge to your OPNsense API using key-based auth
Recommended MCP Servers
Journey fit
Homelab and small-team network appliances are operated continuously after initial setup, which maps to Operate infra work. Infra fits firewall, DNS, DHCP, routing, and certificate tooling on the router itself rather than app-level ship checks.
How it compares
OPNsense router MCP control plane, not a cloud WAF skill or generic penetration-testing toolkit.
Common Questions / FAQ
Who is io.github.itunified-io/opnsense for?
It is for administrators of OPNsense firewalls who want AI assistants to use MCP tools for DNS, firewall, DHCP, routing, VLAN, and ACME tasks.
When should I use io.github.itunified-io/opnsense?
Use it when you routinely adjust homelab or office OPNsense settings and want agent help with documented API operations instead of manual UI steps.
How do I add io.github.itunified-io/opnsense to my agent?
Add npx @itunified.io/mcp-opnsense to MCP stdio config with OPNSENSE_URL, OPNSENSE_API_KEY, OPNSENSE_API_SECRET, and OPNSENSE_VERIFY_SSL if needed.