Ext Ops Panel
Open dashboard
Comparison

Astro Docs vs plannotator-effective-html

Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). plannotator-effective-html is a plugin bundle for AI coding tools published by plannotator. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-07. 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 Docsplannotator-effective-html
Docker MCP Catalog Listed
Version: not stated
Forks (GitHub): 11
Stars (GitHub): 68
Not marked · First seen
Not listed
Community marketplace plannotator/effective-html Not listed Listed
Version: not stated
Forks (GitHub): 278
Stars (GitHub): 4 033
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 plannotator-effective-html
FactAstro Docsplannotator-effective-html
Marketplaces that list it11
Stars (GitHub) (differs)68 (worse)4 033 (better)
Forks (GitHub) (differs)11 (worse)278 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.docs.astro.build/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle8
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/withastro/docs-mcpgithub.com/plannotator/effective-html
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-01
Endpoint at the last check (differs)Responded 22 h agono 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

In its own words, on Docker MCP Catalog:

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

plannotator-effective-html

In its own words, on Community GitHub marketplaces:

Give standalone HTML artifacts a subject-specific visual direction, then create wireframes, styled mockups, interactive prototypes, plans, diagrams, and general artifacts.

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

plannotator-effective-html As a Claude Code plugin

Claude Code
/plugin marketplace add plannotator/effective-html
/plugin install plannotator-effective-html@effective-html

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

Only Astro Docs has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of plannotator-effective-html 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: plannotator-effective-html · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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