Ext Ops Panel
Open dashboard
Comparison

Statsig vs CIPP MCP

Statsig is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). CIPP MCP is an MCP server published by Servosity. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceStatsigCIPP MCP
Cursor: cursor/plugins Listed
Version: 2.0.0
Forks (GitHub): 1 066
Stars (GitHub): 11 026
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.8
Forks (GitHub): 12
Stars (GitHub): 59
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

Statsig vs CIPP MCP
FactStatsigCIPP MCP
Marketplaces that list it11
Stars (GitHub) (differs)11 026 (better)59 (worse)
Forks (GitHub) (differs)1 066 (better)12 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.statsig.com/v3/mcp)On your machine (https://github.com/Servosity/msp-skills/releases/download/cipp-v0.1.8/cipp-mcp.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/servosity/msp-skills
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

Statsig

In its own words, on Cursor: cursor/plugins:

Inspect and manage feature gates, experiments, dynamic configs, and metrics.

CIPP MCP

In its own words, on Official MCP Registry:

First single-binary CLI for CIPP - offline SQLite store, fleet posture analytics, and

How to run each

Statsig

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

CIPP MCP

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

Requires: CIPP_API_KEY (secret), CIPP_BASE_URL

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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 Statsig publish no settings it asks for, so we do not compare settings.

What it can do: Statsig · What it can do: CIPP MCP · 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