PRTG Network Monitor MCP vs Auvik
PRTG Network Monitor MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Auvik is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  PRTG Network Monitor MCP |  Auvik |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Forks (GitHub): 17 Stars (GitHub): 72 Not marked · First seen |
Listed Version: 1.4.6 Forks (GitHub): 4 Stars (GitHub): 1 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 | PRTG Network Monitor MCP | Auvik |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 72 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 17 (better) | 4 (worse) |
| Last release (differs) | 2026-11-06 | Not published |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/prtg-v0.1.1/prtg-mcp.mcpb) | On your machine (ghcr.io/wyre-ai/auvik-mcp:v1.4.6) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 11, secrets among them: 3 | 6, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/servosity/msp-skills | github.com/wyre-ai/auvik-mcp |
| Changes in the last 7 days (differs) | 7 | 0 |
| First seen (differs) | 2026-11-05 | 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
PRTG Network Monitor MCP
Every PRTG API v2 endpoint, plus a fleet view across every client's PRTG core: alarms, status
Auvik
MCP server for the Auvik network monitoring API — devices, alerts, statistics, billing.
How to run each
PRTG Network Monitor MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install prtg@msp-skillsRequires: PRTG_API_KEY (secret), PRTG_FLEET_KEYS (secret), PRTG_MCP_HTTP_TOKEN (secret), PRTG_SERVER
Auvik As a local MCP server: Docker image
claude mcp add --env "AUVIK_API_KEY=<YOUR_AUVIK_API_KEY>" --env "AUVIK_USERNAME=<YOUR_AUVIK_USERNAME>" --transport stdio auvik-mcp -- docker run -i --rm -e AUVIK_API_KEY -e AUVIK_USERNAME ghcr.io/wyre-ai/auvik-mcp:v1.4.6Requires: AUVIK_API_KEY (secret), AUVIK_USERNAME
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
Only PRTG Network Monitor MCP asks for
PRINTING_PRESS_CLIENT_PROFILEPRTG_API_KEY (secret)PRTG_BASE_URLPRTG_COREPRTG_FLEET_KEYS (secret)PRTG_MCP_HTTP_TOKEN (secret)PRTG_MCP_READ_ONLYPRTG_NO_LOCAL_DATAPRTG_SERVERPRTG_SKIP_TLS_VERIFYPRTG_USER_AGENT
Only Auvik asks for
AUTH_MODEAUVIK_API_KEY (secret)AUVIK_REGIONAUVIK_USERNAMELOG_LEVELMCP_TRANSPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: PRTG Network Monitor MCP · What it can do: Auvik · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.