Ext Ops Panel
Open dashboard
Comparison

design-with-claude vs studio.dodraft/getdeck

design-with-claude is a plugin bundle for AI coding tools published by imsaif. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). studio.dodraft/getdeck is an MCP server published by dodraft.studio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplacedesign-with-claudestudio.dodraft/getdeck
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
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

design-with-claude vs studio.dodraft/getdeck
Factdesign-with-claudestudio.dodraft/getdeck
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)11No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)2026-10-24Not published
Where it runs (differs)Installs as a plugin bundleRemote server (getdeck.co/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)50Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/imsaif/design-with-claudeNot stated
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days ago

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-with-claude

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

29 specialized design agents as Claude Code commands. Bring expert design knowledge into every coding session - accessibility, motion design, design systems, color theory, dashboard UX, checkout flows, and more. No runtime. No dependencies. No API keys. Just structured design expertise that gives Claude deep, opinionated knowledge in specific design domains.

studio.dodraft/getdeck

In its own words, on Official MCP Registry:

160+ finished slide layouts and 41 themes your agent can search, fetch and build a deck from

How to run each

design-with-claude As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install design-with-claude@claude-community

studio.dodraft/getdeck As a remote MCP server

Claude Code
claude mcp add --transport http getdeck https://getdeck.co/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only studio.dodraft/getdeck 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: design-with-claude · What it can do: studio.dodraft/getdeck · 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 public marketplace files in GitHub repositories of their authors. 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