Skip to main content
Glama
RoxyAPI Astrology MCP server

RoxyAPI Astrology MCP server

Official

Related Servers

Alternatives to RoxyAPI Astrology MCP server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Multi-tradition astrology engine that computes real birth charts, transits, and synastry for AI agents via MCP tools.
      15
      -
    • A
      license
      A
      quality
      C
      maintenance
      Astrology 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.
      12
      75 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      High-precision astrology tools for LLM agents, including natal charts, transits, progressions, synastry, and more, backed by Swiss Ephemeris.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      C
      quality
      B
      maintenance
      Comprehensive 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.
      500
      292 npm
      4
      MIT

    TDQS

    A3.5/5.0

    Scored across 39 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues