Ext Ops Panel
Open dashboard
Comparison

Levels Custom Apparel vs Open Design

Levels Custom Apparel is an MCP server published by levelscustomapparel.com. Marketplaces we read that list it: 1 (Official MCP Registry). Open Design is an MCP server published by feimacode. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
MarketplaceLevels Custom ApparelOpen Design
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.4.0
Downloads/month (npm): 2 951
Downloads/week (npm): 1 108
Forks (GitHub): 102
Stars (GitHub): 1 085
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.4.0
Downloads/month (npm): 2 951
Downloads/week (npm): 1 108
Forks (GitHub): 102
Stars (GitHub): 1 085
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

Levels Custom Apparel vs Open Design
FactLevels Custom ApparelOpen Design
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub1 085
Forks (GitHub) (differs)No figure on GitHub102
Last release (differs)Not published2026-11-08
Where it runs (differs)Remote server (levelscustomapparel.com/mcp)On your machine (@feimacode/open-design-agent-kit-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/feimacode/open-design-agent-kit
Changes in the last 7 days (differs)04
First seen (differs)2026-10-302026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405no 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

Levels Custom Apparel

In its own words, on Official MCP Registry:

Search and price UK custom embroidered and printed clothing. Orders finish on the site.

Open Design

In its own words, on Official MCP Registry:

Make posters, social posts, slides and landing pages with 198 design systems, checks and exports.

How to run each

Levels Custom Apparel As a remote MCP server

Claude Code
claude mcp add --transport http catalogue https://levelscustomapparel.com/mcp

Open Design As a local MCP server: npm package

Claude Code
claude mcp add --env "OPEN_DESIGN_FIGMA_TOKEN=<YOUR_OPEN_DESIGN_FIGMA_TOKEN>" --transport stdio open-design -- npx -y @feimacode/open-design-agent-kit-mcp

Requires: OPEN_DESIGN_FIGMA_TOKEN (secret)

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

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

What it can do: Levels Custom Apparel · What it can do: Open Design · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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