PostHog MCP vs io.github.cyanheads/wikidata-mcp-server
PostHog MCP is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.cyanheads/wikidata-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  PostHog MCP |  io.github.cyanheads/wikidata-mcp-server |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.1 Forks (GitHub): 1 197 Stars (GitHub): 12 306 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 1 085 Downloads/week (npm): 361 Forks (GitHub): 1 Stars (GitHub): 3 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 | PostHog MCP | io.github.cyanheads/wikidata-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 306 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 1 197 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (mcp.posthog.com/mcp) | Remote server (wikidata.caseyjhand.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 9, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/cyanheads/wikidata-mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | Responded 2 days 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
PostHog MCP
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).
io.github.cyanheads/wikidata-mcp-server
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
How to run each
PostHog MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.cyanheads/wikidata-mcp-server As a remote MCP server
claude mcp add --transport http wikidata-mcp-server https://wikidata.caseyjhand.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of PostHog MCP nor its endpoint list any 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: PostHog MCP · What it can do: io.github.cyanheads/wikidata-mcp-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.