Ext Ops Panel
Open dashboard
Comparison

WatchGuard MCP vs io.github.atef-ataya/depwire

WatchGuard MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.atef-ataya/depwire is an MCP server published by atef-ataya. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. 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
MarketplaceWatchGuard MCPio.github.atef-ataya/depwire
Official MCP Registry Listed
Version: 0.1.3
Forks (GitHub): 13
Stars (GitHub): 63
Not marked · First seen
Listed
Version: 1.28.2
Downloads/month (npm): 4 553
Downloads/week (npm): 249
Forks (GitHub): 6
Stars (GitHub): 65
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.28.2
Downloads/month (npm): 4 553
Downloads/week (npm): 249
Forks (GitHub): 6
Stars (GitHub): 65
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

WatchGuard MCP vs io.github.atef-ataya/depwire
FactWatchGuard MCPio.github.atef-ataya/depwire
Marketplaces that list it22
Stars (GitHub) (differs)63 (worse)65 (better)
Forks (GitHub) (differs)13 (better)6 (worse)
Last release (differs)2026-10-23 (better)2026-10-14 (worse)
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/watchguard-v0.1.3/watchguard-mcp.mcpb)On your machine (depwire-cli)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)12, secrets among them: 4Not published
Licence (differs)Apache-2.0BUSL-1.1
Repository (differs)github.com/servosity/msp-skillsgithub.com/depwire/depwire
Changes in the last 7 days (differs)60
First seen (differs)2026-10-162026-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

WatchGuard MCP

In its own words, on Official MCP Registry:

WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer

io.github.atef-ataya/depwire

In its own words, on Official MCP Registry:

Dependency graph + 24 MCP tools. Impact analysis, simulation, security, agent coordination

How to run each

WatchGuard MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install watchguard@msp-skills

Requires: WATCHGUARD_ACCOUNT_ID, WATCHGUARD_API_KEY (secret), WATCHGUARD_CLIENT_ID (secret), WATCHGUARD_CLIENT_SECRET (secret), WATCHGUARD_MCP_HTTP_TOKEN (secret)

io.github.atef-ataya/depwire As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio depwire -- npx -y depwire-cli mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.atef-ataya/depwire publish no settings it asks for, so we do not compare settings.

What it can do: WatchGuard MCP · What it can do: io.github.atef-ataya/depwire · Compare two other plugins

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. Package data comes from the public npm registry (registry.npmjs.org). 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