liquid-dev vs SitesPlaced
liquid-dev is a plugin bundle for AI coding tools published by hamzashahbaz. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SitesPlaced is an MCP server published by sitesplaced.com. 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
| Marketplace |  liquid-dev | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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
| Fact | liquid-dev | SitesPlaced |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (sitesplaced.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hamzashahbaz/liquid-dev | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 29 h ago, requires a key |
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
liquid-dev
Liquid Dev gives Claude Code deep knowledge of Shopify's Liquid templating language, Online Store 2.0 theme architecture, and modern theme development workflows. It bundles a complete Liquid reference (objects, tags, filters, section schemas, metafields, dynamic sources, performance patterns), a theme development guide covering Shopify CLI, Dawn customization, settings schemas, and deployment — plus an opinionated Shopify developer agent that builds production themes with vanilla CSS/JS, merchant-friendly settings, and performance-first defaults. Built by a developer with 13+ years of Shopify experience who got tired of watching AI hallucinate Liquid syntax.
SitesPlaced
Build, edit, and publish real websites and online stores by chatting with your AI assistant.
How to run each
liquid-dev As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install liquid-dev@claude-communitySitesPlaced As a remote MCP server
claude mcp add --transport http sitesplaced https://sitesplaced.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SitesPlaced 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
Neither one's marketplaces publish the settings it asks for.
What it can do: liquid-dev · What it can do: SitesPlaced · 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.