
OPNsense MCP Server
io.github.itunified-ioPublished by GitHub account itunified-iov2026.4.10Updated Oct 24, 2026
OPNsense MCP Server — 72 tools for DNS, Firewall, DHCP, ACME, Routing, VLANs & more
Overview
A local MCP server exposing 72 tools that let an assistant inspect and manage an OPNsense firewall, covering DNS, firewall rules, DHCP, ACME, routing and VLANs.
- What you can do
- Manage firewall configuration, including rules and related settings, through the exposed OPNsense tools. Administer DNS, DHCP and ACME certificate settings on the OPNsense appliance. Work with routing and VLAN configuration. The manifest lists 72 tools in total across these areas, but individual tool names and parameters are not published, so exact operations are unconfirmed.
- When to use it
- Useful when an assistant should help operate an OPNsense firewall from the desktop, for example reviewing or adjusting firewall, DNS, DHCP, routing or VLAN settings without switching to the web interface.
- Requirements
- Runs locally via npx from the npm package, so Node.js is needed. Requires an OPNsense base URL (OPNSENSE_URL), an API key (OPNSENSE_API_KEY) and API secret (OPNSENSE_API_SECRET). OPNSENSE_VERIFY_SSL can be set to false for self-signed certificates. Network access to the OPNsense appliance is required.
Installation
In SourceWeft
- Open OPNsense MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v2026.4.10LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.