Aegis vs OPNSenseMCP
A side-by-side look at the Aegis and OPNSenseMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aegis for security work as a local process; choose OPNSenseMCP for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aegis when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Choose OPNSenseMCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPNSENSE_HOST, OPNSENSE_API_KEY, OPNSENSE_API_SECRET, OPNSENSE_VERIFY_SSL. - You want tools like
firewall_list_rules, firewall_create_rule, firewall_update_rule.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | OPNSENSE_HOSTOPNSENSE_API_KEYOPNSENSE_API_SECRETOPNSENSE_VERIFY_SSL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 92 |
| Directory activity | 3 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View Aegis | View OPNSenseMCP |
Tools & capabilities
Aegis tools
No tool names declared yet. Check the project README from the listing page.
OPNSenseMCP tools 18
firewall_list_rulesList all firewall rulesfirewall_create_ruleCreate a new rulefirewall_update_ruleUpdate existing rulefirewall_delete_ruleDelete a rulefirewall_apply_changesApply pending changesnat_list_outboundList outbound NAT rulesnat_set_modeSet NAT modenat_create_outbound_ruleCreate NAT rulenat_fix_dmzFix DMZ NAT issuesnat_analyze_configAnalyze NAT configurationarp_listList ARP table entriesrouting_diagnosticsDiagnose routing issues- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aegis
{
"mcpServers": {
"getaegis-aegis": {
"command": "npx",
"args": [
"-y",
"@getaegis/cli"
]
}
}
}
OPNSenseMCP
{
"mcpServers": {
"vespo92-opnsensemcp": {
"command": "npx",
"args": [
"-y",
"opnsense-mcp-server"
],
"env": {
"OPNSENSE_HOST": "YOUR_OPNSENSE_HOST_HERE",
"OPNSENSE_API_KEY": "YOUR_OPNSENSE_API_KEY_HERE",
"OPNSENSE_API_SECRET": "YOUR_OPNSENSE_API_SECRET_HERE",
"OPNSENSE_VERIFY_SSL": "YOUR_OPNSENSE_VERIFY_SSL_HERE"
}
}
}
}
Frequently asked questions
Aegis is categorized under Security and uses a local stdio subprocess. OPNSenseMCP belongs to Security and uses a local stdio subprocess. Pick Aegis for security work and OPNSenseMCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Aegis has no declared pricing — check the project's own site. OPNSenseMCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add getaegis-aegis and vespo92-opnsensemcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aegis has a quality signal of 53/100 (Good) with 3 views, 0 installs and 14 GitHub stars. OPNSenseMCP has 61/100 (Good) with 6 views, 0 installs and 92 GitHub stars.