Ext Ops Panel
Open dashboard
Comparison

Hardware Spec Assembly vs SheetsData

Hardware Spec Assembly is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). SheetsData is an MCP server published by octoco-ltd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceHardware Spec AssemblySheetsData
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
Downloads/month (npm): 372
Downloads/week (npm): 210
Forks (GitHub): 1
Stars (GitHub): 13
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

Hardware Spec Assembly vs SheetsData
FactHardware Spec AssemblySheetsData
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)13 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.sheetsdata.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)16Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/danielrosehill/claude-hardware-spec-assembly-plugingithub.com/octoco-ltd/sheetsdata-mcp
Changes in the last 7 days (differs)24
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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

Hardware Spec Assembly

In its own words, on Community GitHub marketplaces:

Define hardware project BOMs with ESP32-first focus — onboarding captures location/vendors/on-hand gear, then skills for spec creation, live web research of parts (AliExpress/Adafruit/etc.), budgeting, sourcing, compatibility checks, wiring specs, PCB design starting points, assembly instructions, 3D-printable suggestions, and AI-generated mockups via fal.ai nano-banana.

SheetsData

In its own words, on Official MCP Registry:

Electronic component datasheets for AI agents: pinouts, specs, package info and design checks.

How to run each

Hardware Spec Assembly As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install hardware-spec-assembly@danielrosehill

SheetsData As a remote MCP server

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

Requires: SHEETSDATA_API_KEY (secret)

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

Only SheetsData has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of Hardware Spec Assembly nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Hardware Spec Assembly publish no settings it asks for, so we do not compare settings.

What it can do: Hardware Spec Assembly · What it can do: SheetsData · Compare two other plugins

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