Ext Ops Panel
Open dashboard
Comparison

Astro Docs vs Facade UI

Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Facade UI is an MCP server published by marcoschulz7. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceAstro DocsFacade UI
Docker MCP Catalog Listed
Version: not stated
Forks (GitHub): 11
Stars (GitHub): 68
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.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

Astro Docs vs Facade UI
FactAstro DocsFacade UI
Marketplaces that list it11
Stars (GitHub) (differs)68 (better)1 (worse)
Forks (GitHub) (differs)11 (better)0 (worse)
Last release (differs)Not published2026-11-02
Where it runs (differs)Remote server (mcp.docs.astro.build/mcp)Remote server (facadeui.com/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/withastro/docs-mcpgithub.com/marcoschulz7/facade-ui
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-11-02
Endpoint at the last check (differs)Status out of date: last check 32 h ago returned HTTP 405Status out of date: last check 46 h ago returned HTTP 405

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

In its own words, on Docker MCP Catalog:

Access the latest Astro web framework documentation, guides, and API references.

Facade UI

In its own words, on Official MCP Registry:

Animated shadcn components and page blocks for local business, real estate and agency websites.

How to run each

Astro Docs As a remote MCP server

Claude Code
claude mcp add --transport http astro-docs https://mcp.docs.astro.build/mcp

Facade UI As a remote MCP server

Claude Code
claude mcp add --transport http facade https://facadeui.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of Facade UI 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: Facade UI · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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