Ext Ops Panel
Open dashboard
Comparison

Astro Docs vs tokalator-glossary

Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). tokalator-glossary is a plugin bundle for AI coding tools published by vfaraji89. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. 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 Docstokalator-glossary
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: e1ab5df
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

Astro Docs vs tokalator-glossary
FactAstro Docstokalator-glossary
Marketplaces that list it11
Stars (GitHub) (differs)66No figure on GitHub
Forks (GitHub) (differs)13No figure on GitHub
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
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/withastro/docs-mcpgithub.com/vfaraji89/tokalator-glossary
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Responded 2 days 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.

tokalator-glossary

In its own words, on Claude Code: claude-plugins-community:

Auto-generates a codebase glossary (symbol index) after /init or on demand. Scans Python, JavaScript, and TypeScript files using AST parsing to map every class, function, and export with file path and line number. The glossary acts as a compressed context layer , Claude can consult it instead of reading files, saving thousands of tokens per session.

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

tokalator-glossary As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tokalator-glossary@claude-community

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 tokalator-glossary 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: tokalator-glossary · 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.

Where the data comes from: how the catalog is built