Ext Ops Panel
Open dashboard
Comparison

Design vs Webcake Landing

Design is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Webcake Landing is an MCP server published by vuluu2k. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceDesignWebcake Landing
Claude: knowledge-work-plugins Listed
Version: 1.2.0
Forks (GitHub): 3 391
Stars (GitHub): 30 009
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.6.0
Downloads/month (npm): 1 512
Downloads/week (npm): 745
Forks (GitHub): 0
Stars (GitHub): 7
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

Design vs Webcake Landing
FactDesignWebcake Landing
Marketplaces that list it11
Stars (GitHub) (differs)30 009 (better)7 (worse)
Forks (GitHub) (differs)3 391 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.toolvn.io.vn/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Parts of the bundle (differs)16Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/vuluu2k/webcake-landing-mcp
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days 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

Design

In its own words, on Claude: knowledge-work-plugins:

Accelerate design workflows — critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs.

Webcake Landing

In its own words, on Official MCP Registry:

Build, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints.

How to run each

Design As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install design@knowledge-work-plugins

Webcake Landing As a remote MCP server

Claude Code
claude mcp add --transport http webcake-landing-mcp https://mcp.toolvn.io.vn/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: PEXELS_API_KEY (secret), WEBCAKE_JWT (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Webcake Landing 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

The marketplaces of Design publish no settings it asks for, so we do not compare settings.

What it can do: Design · What it can do: Webcake Landing · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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