Ext Ops Panel
Open dashboard
Comparison

PostHog MCP vs io.github.RohanMuppa/brightspace

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.RohanMuppa/brightspace is an MCP server published by RohanMuppa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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.RohanMuppa/brightspace
Cursor: cursor/plugins Listed
Version: 1.0.1
Forks (GitHub): 1 107
Stars (GitHub): 11 352
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.13.19
Downloads/month (npm): 19 841
Downloads/week (npm): 4 720
Forks (GitHub): 28
Stars (GitHub): 57
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.RohanMuppa/brightspace
FactPostHog MCPio.github.RohanMuppa/brightspace
Marketplaces that list it11
Stars (GitHub) (differs)11 352 (better)57 (worse)
Forks (GitHub) (differs)1 107 (better)28 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (mcp.posthog.com/mcp)On your machine (brightspace-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/rohanmuppa/brightspace-mcp-server
Changes in the last 7 days (differs)06
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 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.RohanMuppa/brightspace

In its own words, on Official MCP Registry:

D2L Brightspace MCP server: grades, due dates, assignments, announcements and files. Any school.

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.RohanMuppa/brightspace As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio brightspace -- npx -y brightspace-mcp-server

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

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.RohanMuppa/brightspace · 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