Ext Ops Panel
Open dashboard
Comparison

Shopping vs Continente MCP

Shopping is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Continente MCP is an MCP server published by andredelgado. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-02. 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
MarketplaceShoppingContinente MCP
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 2.0.2
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.1
Downloads/month (npm): 1 424
Downloads/week (npm): 1 424
Forks (GitHub): 7
Stars (GitHub): 26
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

Shopping vs Continente MCP
FactShoppingContinente MCP
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)26 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last release (differs)2026-10-22 (worse)2026-10-26 (better)
Where it runs (differs)Installs as a plugin bundleOn your machine (continentept-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)16Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/danielrosehill/claude-shopping-plugingithub.com/andredelgado/continente-mcp
Changes in the last 7 days00
First seen2026-10-152026-10-15

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

Shopping

In its own words, on Community GitHub marketplaces:

Region-specific consumer shopping primitives — find products, compare local vendors, check availability, and generate ranked purchase recommendations. Ships variant scaffolds per supported region and a provisioning skill for fresh shopping workspaces. Marketplace-specific research (Amazon US, AliExpress Israel) now lives in dedicated per-marketplace plugins; the marketplace-plugins skill is the roster.

Continente MCP

In its own words, on Official MCP Registry:

Unofficial Continente.pt shopping: search products, read favorites and orders, manage the cart.

How to run each

Shopping As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install shopping@danielrosehill

Continente MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "CONTINENTE_PASSWORD=<YOUR_CONTINENTE_PASSWORD>" --transport stdio continente-mcp -- npx -y continentept-mcp

Requires: CONTINENTE_PASSWORD (secret)

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

What it can do: Shopping · What it can do: Continente MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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