Astro Docs vs com.nodoicons/nodo-icons
Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.nodoicons/nodo-icons is an MCP server published by nodoicons.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  com.nodoicons/nodo-icons |
|---|---|---|
| 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: 0.1.2 No figure published 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 | com.nodoicons/nodo-icons |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 68 | No figure on GitHub |
| Forks (GitHub) (differs) | 11 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-01 |
| Where it runs (differs) | Remote server (mcp.docs.astro.build/mcp) | On your machine (@nodo-icons/mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/withastro/docs-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-11-01 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | 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.
com.nodoicons/nodo-icons
Search 5,000 Nodo icons, get SVG, React or Vue code. Free Linear style, Pro styles with a license.
How to run each
Astro Docs As a remote MCP server
claude mcp add --transport http astro-docs https://mcp.docs.astro.build/mcpcom.nodoicons/nodo-icons As a local MCP server: npm package
claude mcp add --transport stdio nodo-icons -- npx -y @nodo-icons/mcpCommands 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 com.nodoicons/nodo-icons 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: com.nodoicons/nodo-icons · 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.