Cylera vs PacketFabric
Cylera is an MCP server published by Cylera. Marketplaces we read that list it: 1 (Docker MCP Catalog). PacketFabric is an MCP server published by PacketFabric. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |   Cylera | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ba2c8606725b Forks (GitHub): 1 Pulls (Docker Hub): 10 878 Stars (Docker Hub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.4 Downloads/month (PyPI): 0 Downloads/week (PyPI): 285 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 | Cylera | PacketFabric |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 10 878 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | On your machine (mcp/cylera-mcp-server) | Remote server (mcp.packetfabric.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 3 | 3, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cylera/cylera-mcp-server | github.com/packetfabric/public-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Cylera
Brings context about device inventory, threats, risks and utilization powered by the Cylera Partner API into an LLM.
PacketFabric
Query and manage PacketFabric NaaS: ports, virtual circuits, cloud routers, pricing, metrics.
How to run each
Cylera As a local MCP server: Docker image
claude mcp add --env "CYLERA_BASE_URL=<YOUR_CYLERA_BASE_URL>" --env "CYLERA_PASSWORD=<YOUR_CYLERA_PASSWORD>" --env "CYLERA_USERNAME=<YOUR_CYLERA_USERNAME>" --transport stdio cylera-mcp-server -- docker run -i --rm -e CYLERA_BASE_URL -e CYLERA_PASSWORD -e CYLERA_USERNAME mcp/cylera-mcp-serverRequires: CYLERA_BASE_URL (secret), CYLERA_PASSWORD (secret), CYLERA_USERNAME (secret)
PacketFabric As a remote MCP server
claude mcp add --transport http packetfabric-mcp https://mcp.packetfabric.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: PF_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of PacketFabric publish no list of tools, so we do not compare tools.
Settings each asks for
Only Cylera asks for
CYLERA_BASE_URL (secret)CYLERA_PASSWORD (secret)CYLERA_USERNAME (secret)
Only PacketFabric asks for
PF_ALLOW_WRITESPF_ON_BEHALFPF_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Cylera · What it can do: PacketFabric · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.