Skip to main content

Official MCP server for Divine API's Western Astrology services — Natal, Synastry, Transit, Composite, Progressions

Project description

Divine API - Western Astrology MCP Server

Official MCP server by Divine API for Western Astrology services. Exposes 56 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 (56 tools)

Group Tools Host
Natal 10 astroapi-4 (wheel chart on astroapi-8)
Synastry 13 astroapi-4 (wheel/aspect-table on astroapi-8)
Transit 11 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.
  • 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

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

divineapi_western_astrology_mcp-1.4.2.tar.gz (42.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file divineapi_western_astrology_mcp-1.4.2.tar.gz.

File metadata

File hashes

Hashes for divineapi_western_astrology_mcp-1.4.2.tar.gz
Algorithm Hash digest
SHA256 1061353909330dec109c36b3b77e027a61faa1b4e7747bf73502f0e9038319b8
MD5 356191c9c5a98ae3acac1b90625145be
BLAKE2b-256 e171043dc1fea65f47caf1d721f1ce107b3a0ef143436ae17316b76c4413bceb

See more details on using hashes here.

File details

Details for the file divineapi_western_astrology_mcp-1.4.2-py3-none-any.whl.

File metadata

File hashes

Hashes for divineapi_western_astrology_mcp-1.4.2-py3-none-any.whl
Algorithm Hash digest
SHA256 11a0279a8cbd54383fe02247845860bf1d807cd44a00791d6983ec68a7e26e7f
MD5 bc6d634c6cac3ab5869e430cc1636f90
BLAKE2b-256 140f65927649afe041cdbf3f3a6781ded29c1a68f5a37e93b358db1204620422

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page