Ext Ops Panel
Open dashboard
Comparison

Firewalla vs deco-mcp

Firewalla is an MCP server published by amittell. Marketplaces we read that list it: 1 (Docker MCP Catalog). deco-mcp is a plugin bundle for AI coding tools published by fullo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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

Where each is published
MarketplaceFirewalladeco-mcp
Docker MCP Catalog Listed
Version: sha256:af186f868759
Forks (GitHub): 13
Pulls (Docker Hub): 30 921
Stars (Docker Hub): 0
Stars (GitHub): 39
Not marked · First seen
Not listed
Community marketplace fullo/claude-plugins-marketplace Not listed Listed
Version: 0.1.2
Forks (GitHub): 0
Stars (GitHub): 2
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

Firewalla vs deco-mcp
FactFirewalladeco-mcp
Marketplaces that list it11
Stars (GitHub) (differs)39 (better)2 (worse)
Pulls (Docker Hub) (differs)30 921No figure on Docker Hub
Forks (GitHub) (differs)13 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/firewalla-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)28Not published
Environment variables it asks for (differs)12, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)Not a bundle5
Licence (differs)MITNot stated
Repository (differs)github.com/amittell/firewalla-mcp-servergithub.com/fullo/deco-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-19

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

In its own words, on Docker MCP Catalog:

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.

deco-mcp

In its own words, on Community GitHub marketplaces:

Manage TP-Link Deco mesh routers from Claude Code over the local API. Bundles an MCP server, three read-only diagnostic agents, and the deco-network skill.

How to run each

Firewalla As a local MCP server: Docker image

Claude Code
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-server

Requires: FIREWALLA_MSP_TOKEN (secret)

deco-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add fullo/claude-plugins-marketplace
/plugin install deco-mcp@fullo-plugins

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of deco-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

Only Firewalla asks for

  • FIREWALLA_BOX_ID
  • FIREWALLA_MSP_ID
  • FIREWALLA_MSP_TOKEN (secret)
  • LOG_LEVEL
  • MCP_CACHE_ENABLED
  • MCP_CACHE_TTL
  • MCP_DEBUG_MODE
  • MCP_RATE_LIMIT_MAX_REQUESTS
  • MCP_RATE_LIMIT_WINDOW
  • MCP_READ_ONLY_MODE
  • MCP_WAVE0_ENABLED
  • NODE_ENV

Only deco-mcp asks for

  • DECO_HOST
  • DECO_PASSWORD (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Firewalla · What it can do: deco-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built