Ext Ops Panel
Open dashboard
Comparison

Kong Konnect vs PostHog MCP

Kong Konnect is an MCP server published by Kong. Marketplaces we read that list it: 1 (Docker MCP Catalog). PostHog MCP is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). 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

Where each is published
MarketplaceKong KonnectPostHog MCP
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
Cursor: cursor/plugins Not listed Listed
Version: 1.0.1
Forks (GitHub): 1 066
Stars (GitHub): 11 026
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 PostHog MCP
FactKong KonnectPostHog MCP
Marketplaces that list it11
Stars (GitHub) (differs)45 (worse)11 026 (better)
Pulls (Docker Hub) (differs)19 316No figure on Docker Hub
Forks (GitHub) (differs)17 (worse)1 066 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/kong)Remote server (mcp.posthog.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/kong/mcp-konnectgithub.com/cursor/plugins
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot 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

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.

PostHog MCP

In its own words, on Cursor: cursor/plugins:

Work with PostHog from chat: query product analytics and run SQL, manage feature flags and experiments, triage error tracking issues, and review session replays, surveys, and dashboards (URL-only connector to PostHog's hosted MCP server).

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)

PostHog MCP

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 PostHog MCP publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of PostHog MCP publish no settings it asks for, so we do not compare settings.

What it can do: Kong Konnect · What it can do: PostHog MCP · 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/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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