Skip to main content

Divine API - Western Astrology MCP Server

Official MCP server by Divine API for Western Astrology services. Exposes 57 tools covering natal charts, synastry, transits, composite charts, progressions, planetary returns, prenatal analysis, and advanced natal techniques, backed by the live Divine API (astroapi-4 and astroapi-8 hosts).

Setup

  1. Get your API key and auth token from https://divineapi.com/api-keys
  2. Set environment variables: DIVINE_API_KEY and DIVINE_AUTH_TOKEN
  3. Add to your MCP client configuration (Claude Desktop, Cursor, etc.)

Tool groups (57 tools)

Group Tools Host
Natal 10 astroapi-4 (wheel chart on astroapi-8)
Synastry 13 astroapi-4 (wheel/aspect-table on astroapi-8)
Transit 12 astroapi-4 and astroapi-8
Composite 4 astroapi-8
Advanced natal 11 astroapi-8
Progressions and returns 5 astroapi-8
Prenatal 2 astroapi-8

Notable input details

  • house_system accepts friendly names (placidus, koch, porphyry, regiomontanus, campanus, equal, whole-sign, morinus, alcabitius) or the Swiss Ephemeris single-letter codes (B, C, E, K, M, O, P, R, W). Names are mapped to letter codes before the API call; invalid values fail client-side with the list of accepted names.
  • divine_western_dominants requires method (TRADITIONAL or MODERN).
  • divine_western_fixed_stars_details requires star_list; get valid names from divine_western_fixed_stars_list (which needs no input).
  • Detail endpoints are two-step: divine_western_planet_return_details takes a return_key from divine_western_planet_returns_list, and divine_western_prenatal_details takes a prenatal_key from divine_western_prenatal_list.
  • Transit tools require the transit moment: transit_day/transit_month/transit_year (plus time and location fields where the endpoint needs them) and, for weekly/monthly/full reports, a transit_planet.
  • divine_western_custom_transit computes transits at a fully specified transit moment and place: it takes the natal birth block plus all ten transit-moment fields as required inputs (transit_day/transit_month/transit_year/transit_hour/transit_min/transit_sec and transit_place/transit_lat/transit_lon/transit_tzone). Unlike divine_western_transit_basic, it also accepts the transit place, latitude, longitude, and timezone.
  • API failures raise MCP tool errors (isError: true); plain Error: ... strings are returned only for client-side validation of enum-style inputs.

See CHANGELOG.md for the full history, including the fixes that made 38 previously failing tools work.

Documentation: https://developers.divineapi.com/western-api

Metadata

Release files for divineapi-western-astrology-mcp 1.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for divineapi-western-astrology-mcp 1.5.0
File Size Uploaded Provenance
divineapi_western_astrology_mcp-1.5.0.tar.gz 43.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for divineapi-western-astrology-mcp 1.5.0
File Interpreter ABI Platform
divineapi_western_astrology_mcp-1.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 66.3 kB

Release files / divineapi_western_astrology_mcp-1.5.0.tar.gz

Download URL divineapi_western_astrology_mcp-1.5.0.tar.gz
Size 43.5 kB
Tags Source
SHA-256 checksum
How to use checksums
a6633480be47daf572687b7fa2106ef1e49edf161454bbd427ff454a2f704f0d
BLAKE2b-256 checksum
How to use checksums
966bda4780bc677f31ba5c6f192bca6aeaefa7d639d7f010df7f77616a283b8f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

Release files / divineapi_western_astrology_mcp-1.5.0-py3-none-any.whl

Download URL divineapi_western_astrology_mcp-1.5.0-py3-none-any.whl
Size 22.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0b04174e502303f762199135b856381e9061e52fef92c15a382fc656badbea3b
BLAKE2b-256 checksum
How to use checksums
a29b3bd2a886c9867ed781ed28dc3f5751c407895907dc2a6a4ad7ae648f9201
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

Security for divineapi-western-astrology-mcp 1.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page