c4m vs CloudArch Codeflow
c4m is a plugin bundle for AI coding tools published by cheriftj. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). CloudArch Codeflow is an MCP server published by cloud-arch.ru. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
| Marketplace |  c4m | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 5b24dda Forks (GitHub): 2 Stars (GitHub): 43 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (npm): 129 Downloads/week (npm): 24 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
| Fact | c4m | CloudArch Codeflow |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 43 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@cloud-arch/mcp-codeflow) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cheriftj/c4-model-skill | github.com/lamp-labs/cloud-arch |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-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
c4m
Interactive C4 architecture diagrams (Simon Brown's model) for Claude Code. Five mode-driven workflows — Design (greenfield), Document-code (retro-doc from a repo), Document-prose (from README/ADR/spec), Review (critique an existing diagram), Update (evolve one) — accessed via /c4m:auto, /c4m:design, /c4m:code, /c4m:prose, /c4m:review, /c4m:update. Output is one Markdown document per C4 level with embedded Mermaid; format negotiable (Structurizr DSL, PlantUML) and destination negotiable (filesystem or MCP — Notion, Linear, Drive). Enforces the editorial invariants: technology mandatory on every Container/Component, intent-specific relationship labels, protocol on inter-container links, assumptions kept explicit.
CloudArch Codeflow
Turn a TypeScript codebase into a live animated call-flow diagram on CloudArch.
How to run each
c4m As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install c4m@claude-communityCloudArch Codeflow As a local MCP server: npm package
claude mcp add --env "CLOUDARCH_API_KEY=<YOUR_CLOUDARCH_API_KEY>" --transport stdio cloudarch-codeflow -- npx -y @cloud-arch/mcp-codeflowRequires: CLOUDARCH_API_KEY (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 c4m publish no settings it asks for, so we do not compare settings.
What it can do: c4m · What it can do: CloudArch Codeflow · 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 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.