Ext Ops Panel
Open dashboard
Comparison

get-design-done vs Agent-Native Design

get-design-done is a plugin bundle for AI coding tools published by hegemonart. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agent-Native Design is an MCP server published by BuilderIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplaceget-design-doneAgent-Native Design
Claude Code: claude-plugins-community Listed
Version: 1.14.5
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 665
Stars (GitHub): 7 326
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

get-design-done vs Agent-Native Design
Factget-design-doneAgent-Native Design
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)7 326 (better)
Forks (GitHub) (differs)1 (worse)665 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (design.agent-native.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)5Not published
Parts of the bundle (differs)95Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/hegemonart/get-design-donegithub.com/builderio/agent-native
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

get-design-done

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

Agent-orchestrated design pipeline for Claude Code. Five stages (brief → discover → plan → design → verify), 33 specialized agents, 12 tool connections including Figma, shadcn/ui, and Magic MCP. Takes a design brief from vague idea to verified, shipped code — with explicit decisions, pattern-mapped plans, and goal-backward audits. Solves the "Claude made it look fine but nothing ties together" problem: every token, component, and copy choice is decided, applied, and verified against the original goals.

Agent-Native Design

In its own words, on Official MCP Registry:

Agent-Native design tool - create and edit visual designs with agent assistance

How to run each

get-design-done As a Claude Code plugin

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

Agent-Native Design As a remote MCP server

Claude Code
claude mcp add --transport http agent-native-design https://design.agent-native.com/mcp

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

Only Agent-Native Design 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: get-design-done · What it can do: Agent-Native Design · 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