Kong Konnect vs Conduktor
Kong Konnect is an MCP server published by konghq.com. Marketplaces we read that list it: 1 (Official MCP Registry). Conduktor is an MCP server published by conduktor. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  Conduktor |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 178 Downloads/week (npm): 46 Forks (GitHub): 0 Stars (GitHub): 5 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 | Conduktor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 5 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (global.mcp.konghq.com) | On your machine (@conduktor/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/conduktor/kafka-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 h ago, requires authentication | no remote endpoint we check |
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
Manage Kong Konnect AI and API gateways, routes, plugins, and analytics from your agent.
Conduktor
Read-only Kafka access for AI assistants: topics, consumer groups, schemas, cluster health.
How to run each
Kong Konnect As a remote MCP server
claude mcp add --transport http konnect https://global.mcp.konghq.com/Conduktor
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: CONDUKTOR_API_TOKEN (secret), CONDUKTOR_CONSOLE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Kong Konnect has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Kong Konnect publish no settings it asks for, so we do not compare settings.
What it can do: Kong Konnect · What it can do: Conduktor · Compare two other plugins
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.