Ext Ops Panel
Open dashboard
Comparison

Close vs io.github.codespar/mcp-shopify

Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.codespar/mcp-shopify is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceCloseio.github.codespar/mcp-shopify
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Downloads/month (npm): 99
Downloads/week (npm): 21
Forks (GitHub): 50
Stars (GitHub): 273
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

Close vs io.github.codespar/mcp-shopify
FactCloseio.github.codespar/mcp-shopify
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub273
Forks (GitHub) (differs)No figure on GitHub50
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.close.com/mcp)On your machine (@codespar/mcp-shopify)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/codespar/mcp-dev-latam
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

Close

In its own words, on Docker MCP Catalog:

Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.

io.github.codespar/mcp-shopify

In its own words, on Official MCP Registry:

MCP server for Shopify — Admin REST API (orders, products, customers, inventory, fulfillments)

How to run each

Close

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

Requires: CLOSE_API_KEY (secret)

io.github.codespar/mcp-shopify As a local MCP server: npm package

Claude Code
claude mcp add --env "SHOPIFY_ACCESS_TOKEN=<YOUR_SHOPIFY_ACCESS_TOKEN>" --env "SHOPIFY_SHOP=<YOUR_SHOPIFY_SHOP>" --transport stdio mcp-shopify -- npx -y @codespar/mcp-shopify

Requires: SHOPIFY_ACCESS_TOKEN (secret), SHOPIFY_SHOP

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

Only Close asks for

  • CLOSE_API_KEY (secret)

Only io.github.codespar/mcp-shopify asks for

  • SHOPIFY_ACCESS_TOKEN (secret)
  • SHOPIFY_API_VERSION
  • SHOPIFY_SHOP

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Close · What it can do: io.github.codespar/mcp-shopify · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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