Ext Ops Panel
Open dashboard
Comparison

Kong Konnect vs bunny.net CDN and Shield

Kong Konnect is an MCP server published by Kong. Marketplaces we read that list it: 1 (Docker MCP Catalog). bunny.net CDN and Shield is an MCP server published by fullfatthings. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceKong Konnectbunny.net CDN and Shield
Docker MCP Catalog Listed
Version: sha256:7988d6e1b0bf
Forks (GitHub): 17
Pulls (Docker Hub): 19 986
Stars (Docker Hub): 0
Stars (GitHub): 45
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
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

Kong Konnect vs bunny.net CDN and Shield
FactKong Konnectbunny.net CDN and Shield
Marketplaces that list it11
Stars (GitHub) (differs)45 (better)0 (worse)
Pulls (Docker Hub) (differs)19 986No figure on Docker Hub
Forks (GitHub) (differs)17 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/kong)On your machine (@fullfatthings/bunny-mcp)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/kong/mcp-konnectgithub.com/fullfatthings/bunny-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-04

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

Kong Konnect

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server for interacting with Kong Konnect APIs, allowing AI assistants to query and analyze Kong Gateway configurations, traffic, and analytics.

bunny.net CDN and Shield

In its own words, on Official MCP Registry:

Debug bunny.net CDN pull zones and manage bunny Shield: WAF, rate limits, bot detection, event logs

How to run each

Kong Konnect As a local MCP server: Docker image

Claude Code
claude mcp add --env "KONNECT_ACCESS_TOKEN=<YOUR_KONNECT_ACCESS_TOKEN>" --transport stdio kong -- docker run -i --rm -e KONNECT_ACCESS_TOKEN mcp/kong

Requires: KONNECT_ACCESS_TOKEN (secret)

bunny.net CDN and Shield As a local MCP server: npm package

Claude Code
claude mcp add --env "BUNNY_API_KEY=<YOUR_BUNNY_API_KEY>" --transport stdio bunny-mcp -- npx -y @fullfatthings/bunny-mcp

Requires: BUNNY_API_KEY (secret)

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

Tools each declares

The marketplaces of bunny.net CDN and Shield publish no list of tools, so we do not compare tools.

Settings each asks for

Only Kong Konnect asks for

  • KONNECT_ACCESS_TOKEN (secret)
  • KONNECT_REGION

Only bunny.net CDN and Shield asks for

  • BUNNY_API_KEY (secret)
  • BUNNY_READONLY

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

What it can do: Kong Konnect · What it can do: bunny.net CDN and Shield · 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.

Where the data comes from: how the catalog is built