Ext Ops Panel
Open dashboard
Comparison

PostHog MCP vs Elekto MCP for SQL Server

PostHog MCP is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). Elekto MCP for SQL Server is an MCP server published by elekto-com-br. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplacePostHog MCPElekto MCP for SQL Server
Cursor: cursor/plugins Listed
Version: 1.0.1
Forks (GitHub): 1 268
Stars (GitHub): 12 913
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.3.4
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

PostHog MCP vs Elekto MCP for SQL Server
FactPostHog MCPElekto MCP for SQL Server
Marketplaces that list it11
Stars (GitHub) (differs)12 913 (better)0 (worse)
Forks (GitHub) (differs)1 268 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (mcp.posthog.com/mcp)On your machine (Elekto.Mcp.Sql)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/elekto-com-br/elekto-mcp-sql
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days ago, requires a keyno 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

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).

Elekto MCP for SQL Server

In its own words, on Official MCP Registry:

Read-only SQL Server introspection and querying: schema, definitions, dependencies and data.

How to run each

PostHog MCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Elekto MCP for SQL Server

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.

Only PostHog MCP 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

Neither one's marketplaces publish the settings it asks for.

What it can do: PostHog MCP · What it can do: Elekto MCP for SQL Server · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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