Ext Ops Panel
Open dashboard
Comparison

Astro Docs vs Divine API - Western Astrology

Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Divine API - Western Astrology is an MCP server published by divineapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 DocsDivine API - Western Astrology
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.8.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

Astro Docs vs Divine API - Western Astrology
FactAstro DocsDivine API - Western Astrology
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)Remote server (mcp.divineapi.com/western/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-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot 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

In its own words, on Docker MCP Catalog:

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

Divine API - Western Astrology

In its own words, on Official MCP Registry:

Official Divine API MCP for Western Astrology: Natal, Synastry, Transit, Composite, Progressions.

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

Divine API - Western Astrology As a remote MCP server

Claude Code
claude mcp add --transport http western https://mcp.divineapi.com/western/mcp --header "X-Divine-Api-Key: <YOUR_X_DIVINE_API_KEY>" --header "X-Divine-Auth-Token: <YOUR_X_DIVINE_AUTH_TOKEN>"

Requires: X-Divine-Api-Key header, X-Divine-Auth-Token header

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

Tools each declares

The marketplaces of Divine API - Western Astrology 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: Divine API - Western Astrology · 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