Astro Docs vs backend-design
Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). backend-design is a plugin bundle for AI coding tools published by sheitabrk. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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 |  Astro Docs |  backend-design |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated Forks (GitHub): 13 Stars (GitHub): 66 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | Astro Docs | backend-design |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 66 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.docs.astro.build/mcp) | Installs as a plugin bundle |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 3 |
| Parts of the bundle (differs) | Not a bundle | 25 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/withastro/docs-mcp | github.com/sheitabrk/backend-design |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
Astro Docs
Access the latest Astro web framework documentation, guides, and API references.
backend-design
Claude learns senior backend reflexes: load awareness, idempotency, security audits, migration safety, and incident-grade observability. Backend counterpart to Frontend Design. Forces a 6-step senior workflow before any server-side code (endpoint, worker, CLI, consumer, cron, integration). Adds disciplines for data modeling, migrations, queries, idempotency, error handling, observability, performance, security, auth, debugging, and testing.
How to run each
Astro Docs As a remote MCP server
claude mcp add --transport http astro-docs https://mcp.docs.astro.build/mcpbackend-design As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install backend-design@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of backend-design publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Astro Docs · What it can do: backend-design · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.