MCP Server

Started by HappyDoer, Today at 12:39:39 AM

Previous topic - Next topic
Has there been any consideration of an official MCP (Model Context Protocol) server for OPNsense? MCP is the open standard AI assistants (Claude, ChatGPT, Copilot, local LLMs etc.) use to talk to external tools, and since OPNsense already has a comprehensive REST API it seems a natural fit.

This could be either a first-class project or a vetted community project linked from the documentation's "Community Plugins > Other" list.

From a quick review, these are the most developed projects at the moment:


An official server would help me with:

  • Security and trust - a firewall is the last place you want an unvetted tool holding admin credentials. An official server could use the API only, with least-privilege API users and a clear read-only mode, rather than relying on SSH or shell access.
  • Keeping up with releases - community servers fall behind as the API changes between releases. If one was maintained alongside OPNsense, it would track those changes.
  • Troubleshooting and auditing - asking "why can't VLAN 20 reach the NAS?" or "which rules are unused or overlapping?" and getting an answer based on the live config, logs and states.
  • Safer changes - describing a change in plain language, then reviewing the exact rules, aliases or NAT entries proposed before they are applied.

A quick GitHub search already turns up 42 OPNsense MCP server projects, so there's clearly demand. Unfortunately, effort is spread across many partial implementations rather than one complete, up-to-date server. Would the team consider either building one or working with an external maintainer to list a recommended community option in the docs?