Firewalla vs Auvik MCP
Firewalla is an MCP server published by amittell. Marketplaces we read that list it: 1 (Docker MCP Catalog). Auvik MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Firewalla |   Auvik MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:af186f868759 Forks (GitHub): 13 Pulls (Docker Hub): 30 865 Stars (Docker Hub): 0 Stars (GitHub): 39 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.5 Forks (GitHub): 13 Stars (GitHub): 59 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Firewalla | Auvik MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 39 (worse) | 59 (better) |
| Pulls (Docker Hub) (differs) | 30 865 | No figure on Docker Hub |
| Forks (GitHub) | 13 | 13 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/firewalla-mcp-server) | On your machine (https://github.com/Servosity/msp-skills/releases/download/auvik-v0.2.5/auvik-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 12, secrets among them: 1 | 6, secrets among them: 1 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/amittell/firewalla-mcp-server | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Firewalla
Real-time network monitoring, security analysis, and firewall management through 28 specialized tools. Access security alerts, network flows, device status, and firewall rules directly from your Firewalla device.
Auvik MCP
Every Auvik endpoint as a command, plus the cross-client answers the Auvik UI and API cannot give
How to run each
Firewalla As a local MCP server: Docker image
claude mcp add --env "FIREWALLA_MSP_TOKEN=<YOUR_FIREWALLA_MSP_TOKEN>" --transport stdio firewalla-mcp-server -- docker run -i --rm -e FIREWALLA_MSP_TOKEN mcp/firewalla-mcp-serverRequires: FIREWALLA_MSP_TOKEN (secret)
Auvik MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install auvik@msp-skillsRequires: AUVIK_API_KEY (secret), AUVIK_BASE_URL, AUVIK_USERNAME
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Auvik MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only Firewalla asks for
FIREWALLA_BOX_IDFIREWALLA_MSP_IDFIREWALLA_MSP_TOKEN (secret)LOG_LEVELMCP_CACHE_ENABLEDMCP_CACHE_TTLMCP_DEBUG_MODEMCP_RATE_LIMIT_MAX_REQUESTSMCP_RATE_LIMIT_WINDOWMCP_READ_ONLY_MODEMCP_WAVE0_ENABLEDNODE_ENV
Only Auvik MCP asks for
AUVIK_API_KEY (secret)AUVIK_BASE_URLAUVIK_TENANTAUVIK_USERNAMEAUVIK_USER_AGENTPRINTING_PRESS_CLIENT_PROFILE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Firewalla · What it can do: Auvik MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.