Ext Ops Panel
Open dashboard
Comparison

architect-system-design vs io.github.xmpuspus/cloudwright

architect-system-design is a plugin bundle for AI coding tools published by Seth Ford. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.xmpuspus/cloudwright is an MCP server published by xmpuspus. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. 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
Marketplacearchitect-system-designio.github.xmpuspus/cloudwright
Community marketplace sethdford/claude-skills Listed
Version: 1.0.0
Forks (GitHub): 9
Stars (GitHub): 47
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.10.0
Downloads/month (PyPI): 274
Downloads/week (PyPI): 82
Forks (GitHub): 2
Stars (GitHub): 33
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.10.0
Downloads/month (PyPI): 274
Downloads/week (PyPI): 82
Forks (GitHub): 2
Stars (GitHub): 33
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

architect-system-design vs io.github.xmpuspus/cloudwright
Factarchitect-system-designio.github.xmpuspus/cloudwright
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)47 (better)33 (worse)
Forks (GitHub) (differs)9 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (cloudwright-ai-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)14Not a bundle
LicenceMITMIT
Repository (differs)github.com/sethdford/claude-skillsgithub.com/xmpuspus/cloudwright
Changes in the last 7 days (differs)20
First seen (differs)2026-11-052026-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

architect-system-design

In its own words, on Community GitHub marketplaces:

Architecture patterns, system decomposition, DDD, microservices, event-driven, CQRS. Grounded in TOGAF, IASA BTABoK, ISO 42010.

io.github.xmpuspus/cloudwright

In its own words, on Official MCP Registry:

Cloud architecture and migration planning with costs, controls, evidence, and deployable IaC.

How to run each

architect-system-design As a Claude Code plugin

Claude Code
/plugin marketplace add sethdford/claude-skills
/plugin install architect-system-design@claude-skills

io.github.xmpuspus/cloudwright As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cloudwright -- uvx cloudwright-ai-mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: architect-system-design · What it can do: io.github.xmpuspus/cloudwright · 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. Package data comes from the Python Package Index (pypi.org). 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