Kong Konnect vs Axiom Relay
Kong Konnect is an MCP server published by Kong. Marketplaces we read that list it: 1 (Docker MCP Catalog). Axiom Relay is an MCP server published by Itr3k. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  Kong Konnect |  Axiom Relay |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7988d6e1b0bf Forks (GitHub): 17 Pulls (Docker Hub): 19 920 Stars (Docker Hub): 0 Stars (GitHub): 45 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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
| Fact | Kong Konnect | Axiom Relay |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 45 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 19 920 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 17 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/kong) | Remote server (axiomrelay.io/mcp/discovery) |
| Transport (differs) | stdio | Streamable HTTP |
| 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 | Not stated |
| Repository (differs) | github.com/kong/mcp-konnect | github.com/itr3k/axiom-relay-discovery |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 13 h ago |
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.
Axiom Relay
Free agent-service discovery, OpenAPI document checks, and receipt verification. No API key needed.
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)
Axiom Relay As a remote MCP server
claude mcp add --transport http axiom-relay-discovery https://axiomrelay.io/mcp/discoveryCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Axiom Relay has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Axiom Relay publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Axiom Relay publish no settings it asks for, so we do not compare settings.
What it can do: Kong Konnect · What it can do: Axiom Relay · 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.