astrolog-mcp
Related Servers
Alternatives to astrolog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to compute deterministic astrological data with Swiss Ephemeris, including natal charts, transits, synastry, and birth-place resolution, so they never invent planetary positions.458 npmMIT
- 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
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to access structured GetBirthChart astrology calculations such as natal charts, planet positions, the big three, moon sign, rising sign, aspects, and synastry through the public API.745 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access real-time Vedic astrology data and perform calculations like horoscopes, panchang, matchmaking, and planetary positions via the AstroChalit API.504 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables users to resolve birthplaces and calculate natal charts, transits, aspects, and ephemeris positions using Swiss Ephemeris, returning structured numerical results without LLM generation or natal-history storage.AGPL 3.0
TDQS
Scored across 5 tools
The tools are largely distinct: natal chart, composite chart, harmonic midpoints, moment transits, and daily transits. The only notable overlap is get_transit_data versus get_daily_transits, both transit calculations, though the descriptions clearly separate a single moment from a whole local day.
All five tools use a consistent get_<noun phrase> pattern in snake_case. The minor variation between _data suffixes and direct nouns does not break the predictable convention.
Five tools is well-scoped for a focused astrology calculation server. Each tool covers a distinct chart or transit operation, with no filler or redundant entries.
The surface covers core natal, transit, daily transit, composite, and harmonic midpoint workflows. Notable gaps remain, such as synastry between two natal charts, progressions, and return charts, but core chart-data retrieval is well covered.