PostHog MCP vs MCP Search Console
PostHog MCP is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). MCP Search Console is an MCP server published by Ayo-Fam. 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 |  MCP Search Console |
|---|---|---|
| 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: 0.1.3 Downloads/month (PyPI): 103 Downloads/week (PyPI): 29 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 | PostHog MCP | MCP Search Console |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 913 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 268 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.posthog.com/mcp) | On your machine (mcp-search-console-multi) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, 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/apexradius/mcp-search-console |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | 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
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).
MCP Search Console
Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.
How to run each
PostHog MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MCP Search Console As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-search-console -- uvx mcp-search-console-multiCommands 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
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: MCP Search Console · 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.