Ext Ops Panel
Open dashboard
Comparison

PostHog MCP vs io.github.neptun2000/heor-agent

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.neptun2000/heor-agent is an MCP server published by neptun2000. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 MCPio.github.neptun2000/heor-agent
Cursor: cursor/plugins Listed
Version: 1.0.1
Forks (GitHub): 1 133
Stars (GitHub): 11 569
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.35.0
Downloads/month (npm): 3 039
Downloads/week (npm): 112
Forks (GitHub): 2
Stars (GitHub): 9
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 io.github.neptun2000/heor-agent
FactPostHog MCPio.github.neptun2000/heor-agent
Marketplaces that list it11
Stars (GitHub) (differs)11 569 (better)9 (worse)
Forks (GitHub) (differs)1 133 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.posthog.com/mcp)On your machine (heor-agent-mcp)
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/neptun2000/heor-agent-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 36 h 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).

io.github.neptun2000/heor-agent

In its own words, on Official MCP Registry:

HEOR MCP server: literature search, CEA, BIA, NMA/MAIC, HTA dossiers (NICE/FDA/EMA/JCA).

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.neptun2000/heor-agent As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio heor-agent -- npx -y heor-agent-mcp

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: io.github.neptun2000/heor-agent · 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