Ext Ops Panel
Open dashboard
Comparison

stitch-to-nextjs vs Master CSS

stitch-to-nextjs is a plugin bundle for AI coding tools published by yshaish1. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Master CSS is an MCP server published by master-co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacestitch-to-nextjsMaster CSS
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.3
Forks (GitHub): 45
Stars (GitHub): 1 957
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

stitch-to-nextjs vs Master CSS
Factstitch-to-nextjsMaster CSS
Marketplaces that list it11
Stars (GitHub) (differs)11 (worse)1 957 (better)
Forks (GitHub) (differs)2 (worse)45 (better)
Last release (differs)Not published2026-11-11
Where it runs (differs)On your machine (@_davideast/stitch-mcp)On your machine (@master/css-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/yshaish1/stitch-to-nextjsgithub.com/master-co/css
Changes in the last 7 days (differs)05
First seen (differs)2026-10-122026-11-07

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

stitch-to-nextjs

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

Convert Google Stitch designs into pixel-perfect Next.js + Tailwind CSS components. Extracts exact HTML/CSS, downloads images, maps all 29 Stitch fonts to next/font/google, preserves exact colors and spacing (never rounds to Tailwind defaults), and auto-configures the stitch-mcp server for HTML code export and screenshot validation. Supports ShadCN/UI mapping, Tailwind v3/v4, and Server Components.

Master CSS

In its own words, on Official MCP Registry:

Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.

How to run each

stitch-to-nextjs As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install stitch-to-nextjs@claude-community

Master CSS As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio master-css -- npx -y @master/css-mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: stitch-to-nextjs · What it can do: Master CSS · 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