RoxyAPI Astrology MCP server
OfficialRelated Servers
Alternatives to RoxyAPI Astrology MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMulti-tradition astrology engine that computes real birth charts, transits, and synastry for AI agents via MCP tools.15-
- AlicenseAqualityCmaintenanceAstrology MCP server that computes natal charts, transits, synastry, progressions, returns, eclipses, retrogrades, and moon phases from a real ephemeris, enabling AI agents to provide accurate astrological calculations without hallucination.1275 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to compute ephemeris-grade natal charts, current transits, and zodiac sign profiles through deterministic astrology tools.MIT
- AlicenseNot gradedqualityBmaintenanceHigh-precision astrology tools for LLM agents, including natal charts, transits, progressions, synastry, and more, backed by Swiss Ephemeris.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients and LLMs to compute Vedic astrology charts, including 47 ayanamsha modes, 20 divisional charts, Vimshottari dasha, transits, Panchanga, and related calculations from birth details. It also resolves places to timezone and coordinates and exposes configuration and server-status tools.AGPL 3.0

astroway-mcpofficial
AlicenseCqualityBmaintenanceComprehensive astrology MCP exposing every endpoint of the AstroWay Calculation API — natal charts, synastry, transits, Vedic dashas, Tarot, Numerology, Human Design. Sub-arcsecond Swiss Ephemeris precision, 10 000 free credits per month.500292 npm4MIT
TDQS
Scored across 39 tools
Most tools target distinct astrology calculations, but several pairs overlap heavily: synastry vs. compatibility_score, transits vs. transit_aspects, and natal_chart vs. planets/houses/aspects. The descriptions usually clarify the boundaries, but an agent could still misselect among the multiple transit, aspect, and relationship-compatibility endpoints.
Tool names consistently follow a snake_case get_astrology_* or post_astrology_* pattern, with predictable resource-oriented suffixes such as _monthly, _id, and _chart. The names are long but follow one coherent convention throughout.
At 39 tools, the surface is heavy for an MCP server even though the astrology domain is broad. Many endpoints are useful, but the set exceeds a well-scoped size and increases selection burden.
The surface covers natal charts, transits, returns, progressions, relationship charts, horoscopes, lunar phases, astrocartography, fixed stars, and reference data. For a Western astrology API, there are no obvious core lifecycle gaps.