Ext Ops Panel
Open dashboard
Comparison

figma-suite vs io.github.Maher-Reven/asdesigned

figma-suite is a plugin bundle for AI coding tools published by robukh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Maher-Reven/asdesigned is an MCP server published by Maher-Reven. 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
Marketplacefigma-suiteio.github.Maher-Reven/asdesigned
Claude Code: claude-plugins-community Listed
Version: 1.4.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 360
Downloads/week (npm): 25
Forks (GitHub): 0
Stars (GitHub): 0
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

figma-suite vs io.github.Maher-Reven/asdesigned
Factfigma-suiteio.github.Maher-Reven/asdesigned
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (asdesigned)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MPL-2.0Not stated
Repository (differs)github.com/robukh/figma-suitegithub.com/maher-reven/asdesigned
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

figma-suite

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

Design production-quality screens in Figma using your design system — every property variable-bound, every element a component instance. Build and edit Figma component libraries from code, sync design tokens bidirectionally (code ↔ Figma), and audit files for design system compliance. Requires the official Figma MCP server.

io.github.Maher-Reven/asdesigned

In its own words, on Official MCP Registry:

Diff a rendered UI element against its Figma source and get every drifted property with its delta.

How to run each

figma-suite As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install figma-suite@claude-community

io.github.Maher-Reven/asdesigned As a local MCP server: npm package

Claude Code
claude mcp add --env "FIGMA_TOKEN=<YOUR_FIGMA_TOKEN>" --transport stdio asdesigned -- npx -y asdesigned asdesigned-mcp

Requires: FIGMA_TOKEN (secret)

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

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

What it can do: figma-suite · What it can do: io.github.Maher-Reven/asdesigned · 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