Ext Ops Panel
Open dashboard
Comparison

naksha-studio vs Smasher Studio — AI Fashion Design

naksha-studio is a plugin bundle for AI coding tools published by Adityaraj0421. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Smasher Studio — AI Fashion Design is an MCP server published by Atenkai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacenaksha-studioSmasher Studio — AI Fashion Design
Claude Code: claude-plugins-community Listed
Version: 5.1.1
Forks (GitHub): 27
Stars (GitHub): 345
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

naksha-studio vs Smasher Studio — AI Fashion Design
Factnaksha-studioSmasher Studio — AI Fashion Design
Marketplaces that list it11
Stars (GitHub) (differs)345No figure on GitHub
Forks (GitHub) (differs)27No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (www.smasher.studio/mcp/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)74Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/adityaraj0421/naksha-studiogithub.com/atenkai/smasher-studio-client
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 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

naksha-studio

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

A virtual design team for Claude Code, Cursor, Windsurf, Gemini CLI, and Copilot — 18 roles, 32 commands, 11,000+ lines of expert design knowledge. Your agency's design brain, inside your terminal.

Smasher Studio — AI Fashion Design

In its own words, on Official MCP Registry:

AI fashion design — product photos, videos, tech packs, colorways & fabric sims.

How to run each

naksha-studio As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install naksha-studio@claude-community

Smasher Studio — AI Fashion Design As a remote MCP server

Claude Code
claude mcp add --transport http smasher-studio https://www.smasher.studio/mcp/mcp

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

Only Smasher Studio — AI Fashion 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: naksha-studio · What it can do: Smasher Studio — AI Fashion 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