OPNsense MCP Server — 72 tools for DNS, Firewall, DHCP, ACME, Routing, VLANs & more
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-itunified-io-opnsense": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Slim OPNsense MCP Server for managing firewall infrastructure via the OPNsense REST API.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / security
MCP server for using the GitLab API
An evil MCP server used for redteam testing
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
Enhanced MCP server for GitLab: group projects listing and activity tracking
MCP Security Weekly
Get CVE alerts and security updates for io.github.itunified-io/opnsense and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Slim OPNsense MCP Server for managing firewall infrastructure via the OPNsense REST API.
No SSH. No shell execution. API-only. 3 runtime dependencies.
For audit + compliance reporting, multi-firewall fleet operations, encrypted backup orchestration, capacity forecasting, advanced IDS tuning, and Q-Feeds Premium feeds, see the commercial tier:
mcp-opnsense-enterprise— €29/month/seat
Tier comparison:
| Tier | This repo | Enterprise repo |
|---|---|---|
| License | AGPL-3.0-only | Commercial (Ed25519 JWT) |
| Pricing | Free | €29/mo/seat |
| Tools | 112 (basic CRUD + diagnostics) | + ~35 (audit, compliance, fleet, backup_ops, capacity, ha, ids_advanced, qfeeds_premium) |
| Use case | Single-firewall ops | Multi-firewall + audit/compliance workflows |
Trial token: sales@itunified.io.
62 tools across 8 domains:
npm install
cp .env.example .env # Edit with your OPNsense API credentials
npm run build
node dist/index.js # stdio transport for MCP
mcp-opnsense supports opportunistic AppRole authentication against a HashiCorp Vault
instance. When Vault env vars are present, the server fetches OPNsense credentials from
KV v2 at startup. If they are absent, the server falls back silently to direct env vars or
MCP_SECRETS_FILE — no configuration change or restart required.
NAS_VAULT_ADDR in process.env.NAS_VAULT_ROLE_ID + NAS_VAULT_SECRET_ID),
reads the secret at <NAS_VAULT_KV_MOUNT>/data/<path>, and maps the KV fields to
OPNsense env vars.NAS_VAULT_ADDR is not set (or any Vault call fails), a single warning line is
written to stderr and the server continues with whatever env vars are already available.