The mcp-opnsense is a slim MCP server designed for managing firewall infrastructure using the OPNsense REST API without SSH or shell execution.
From the registry: OPNsense MCP Server — 72 tools for DNS, Firewall, DHCP, ACME, Routing, VLANs & more
Please install the `opnsense` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **OPNsense instance with API access** — Requires an OPNsense firewall with API key and secret configured (https://docs.opnsense.org/development/how-tos/api.html)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["@itunified.io/mcp-opnsense"]
- required environment variables:
- `OPNSENSE_URL`: OPNsense base URL (example: `https://192.168.1.1`)
- `OPNSENSE_API_KEY`: API key for authentication (example: `<your-api-key>`)
- `OPNSENSE_API_SECRET`: API secret for authentication (example: `<your-api-secret>`)
- optional environment variables:
- `OPNSENSE_VERIFY_SSL`: Set to false for self-signed certificates (example: `true`)
- `OPNSENSE_TIMEOUT`: Request timeout in milliseconds (example: `30000`)
- `MCP_SECRETS_FILE`: Path to a key/value file to load credentials at startup (example: `~/.mcp-opnsense.env`)
Note: 87 tools across 8 domains (DNS, firewall, diagnostics, interfaces, DHCP, system, ACME, firmware). Supports optional HashiCorp Vault integration for secrets. SSH-backed tools available for interface assignment. Node.js >= 20 required.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.OPNSENSE_URLrequiredOPNsense base URL (e.g. `https://192.168.1.1`)OPNSENSE_API_KEYrequiredAPI key for authenticationOPNSENSE_API_SECRETrequiredAPI secret for authenticationManage UniFi Access doors, credentials, policies, visitors, and events via MCP.