Astro Docs vs StyleForge-AI
Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). StyleForge-AI is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated Forks (GitHub): 13 Stars (GitHub): 66 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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 | StyleForge-AI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 66 | No figure on GitHub |
| Forks (GitHub) (differs) | 13 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.docs.astro.build/mcp) | Remote server (styleforge-ai-mcp.vercel.app/api/mcp) |
| Transport (differs) | Streamable HTTP | SSE |
| 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 | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 21 h ago | not checked yet |
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.
StyleForge-AI
Automated design token builder producing clean CSS and Sass assets.
How to run each
Astro Docs As a remote MCP server
claude mcp add --transport http astro-docs https://mcp.docs.astro.build/mcpStyleForge-AI As a remote MCP server
claude mcp add --transport sse styleforge-ai https://styleforge-ai-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
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 StyleForge-AI 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: StyleForge-AI · 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.