Ext Ops Panel
Open dashboard
Comparison

lcontext vs io.github.sudomichael/gizmoanalytics

lcontext is a plugin bundle for AI coding tools published by Lcontext. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.sudomichael/gizmoanalytics is an MCP server published by sudomichael. 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
Marketplacelcontextio.github.sudomichael/gizmoanalytics
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Downloads/month (npm): 130
Downloads/week (npm): 27
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

lcontext vs io.github.sudomichael/gizmoanalytics
Factlcontextio.github.sudomichael/gizmoanalytics
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (lcontext-mcp)On your machine (gizmoanalytics-mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/lcontext/lcontextgithub.com/sudomichael/analyticsautopilot
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

lcontext

In its own words, on Claude Code: claude-plugins-community:

Product analytics for AI coding agents. Understand how users navigate your app — where they engage, hesitate, and drop off — then connect behavioral insights directly to code changes.

io.github.sudomichael/gizmoanalytics

In its own words, on Official MCP Registry:

Cookieless analytics for AI coding agents. Install in one prompt, 28 tools, OAuth onboarding.

How to run each

lcontext As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install lcontext@claude-community

io.github.sudomichael/gizmoanalytics

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

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 io.github.sudomichael/gizmoanalytics publish no settings it asks for, so we do not compare settings.

What it can do: lcontext · What it can do: io.github.sudomichael/gizmoanalytics · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-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