OPNsense MCP Server — 72 tools for DNS, Firewall, DHCP, ACME, Routing, VLANs & more
{
"mcpServers": {
"io-github-itunified-io-opnsense": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
OPNsense MCP Server — 72 tools for DNS, Firewall, DHCP, ACME, Routing, VLANs & more
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 2 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
Search, evaluate, and compare 17,000+ MCP servers — each scored on security, maintenance, and efficiency.
MCP server for using the REMnux malware analysis toolkit via AI assistants
🌱 Agricultural AI: Soil analysis, crop recommendations, weather forecasts. FREE TurboQuant.
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.
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.fetch built into Node 20+ — no additional runtime
dependencies are added.Explicit env vars > Vault > MCP_SECRETS_FILE > error (required var missing)
process.env are never overwritten by Vault.NAS_VAULT_ADDR is unset.MCP_SECRETS_FILE is the last fallback (see Loading Secrets from a File below).| Variable | Required | Description |
|---|---|---|
NAS_VAULT_ADDR | Yes* | Vault server address (e.g. https://vault.example.com:8200) |
NAS_VAULT_ROLE_ID | Yes* | AppRole role ID for this server |
NAS_VAULT_SECRET_ID | Yes* | AppRole secret ID for this server |
| `NAS_VAULT |