Kong Konnect vs connector-namespaces
Kong Konnect is an MCP server published by Kong. Marketplaces we read that list it: 1 (Docker MCP Catalog). connector-namespaces is a plugin bundle for AI coding tools published by Azure. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7988d6e1b0bf Forks (GitHub): 17 Pulls (Docker Hub): 19 316 Stars (Docker Hub): 0 Stars (GitHub): 45 Not marked · First seen |
Not listed |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 1.2.0 Forks (GitHub): 7 Stars (GitHub): 20 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 | Kong Konnect | connector-namespaces |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 45 (better) | 20 (worse) |
| Pulls (Docker Hub) (differs) | 19 316 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 17 (better) | 7 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/kong) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/kong/mcp-konnect | github.com/azure/connectors |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
Kong Konnect
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.
connector-namespaces
Interactive GitHub Copilot canvas for discovering, connecting, and managing hosted MCP servers from an Azure Connector Namespace.
How to run each
Kong Konnect As a local MCP server: Docker image
claude mcp add --env "KONNECT_ACCESS_TOKEN=<YOUR_KONNECT_ACCESS_TOKEN>" --transport stdio kong -- docker run -i --rm -e KONNECT_ACCESS_TOKEN mcp/kongRequires: KONNECT_ACCESS_TOKEN (secret)
connector-namespaces
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of connector-namespaces publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of connector-namespaces publish no settings it asks for, so we do not compare settings.
What it can do: Kong Konnect · What it can do: connector-namespaces · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.