Asterwise

What Asterwise does

The Asterwise MCP server exposes 118 tools for astrology and related divination systems. Its largest areas include Western astrology, Vedic natal analysis, Dasha calculations, matchmaking, Panchanga, numerology, tarot, crystals, dreams, and reference data. The Asterwise MCP server is therefore suited to agents that need calculation results as structured tool responses rather than free-form astrological commentary alone.

Natal tools can calculate sidereal charts with planets, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata. Other tools calculate sixteen divisional charts, Shadbala, Bhavbala, Vimshopaka, Ashtakavarga, yogas, doshas, Sade Sati, and special ascendant information. Timing tools cover Vimshottari, Char, Yogini, and Ashtottari Dasha, along with Dasha-transit correlations and annual Tajika solar returns.

Matchmaking tools implement several traditions, including North Indian Ashtakoota, Dashakoot, Tamil Porutham, Thirumana Porutham, and Papasamyam. Panchanga tools provide daily limbs, sunrise-based timings, Choghadiya, Hora, and Rahu Kaal. The repository also describes Western charts, transits, returns, progressions, planetary hours, numerology profiles, tarot spreads, crystal references, angel numbers, and dream references.

How it works

The hosted MCP endpoint is https://mcp.asterwise.com/mcp. Clients can send an API key as a Bearer token or through the X-API-Key header. OAuth 2.1 is also available, including authorization-code flow with PKCE for supported MCP clients. A health endpoint is available at /health.

Most chart tools accept birth date, time, latitude, longitude, and an ayanamsa where applicable. Dates use YYYY-MM-DD, times use HH:MM, and coordinates are bounded by valid latitude and longitude ranges. Unknown birth times should be omitted, not replaced with 00:00; some calculations then use a sunrise chart and mark the birth time as unavailable. KP chart and Dasha-transit tools require a known birth time.

The Asterwise MCP server validates many inputs locally before forwarding requests to the Asterwise API. Tool outputs have system-specific response shapes, so consumers should distinguish, for example, Vimshottari period arrays from Yogini and Ashtottari data.periods.root trees.

Setup and configuration

For Claude Desktop, configure mcp-remote with the hosted MCP URL and pass the API key through MCP_HEADER_AUTHORIZATION. Cursor can use the same URL directly with an Authorization header. The README also identifies VS Code as an OAuth MCP client.

A local HTTP deployment uses Python dependencies, uvicorn server:app, and ASTERWISE_API_BASE_URL. OAuth token issuance additionally requires JWT_SECRET; OAuth deployments may also need MCP_OAUTH_SECRET, INTERNAL_API_TOKEN, and FRONTEND_URL. For stdio, run python stdio.py after setting ASTERWISE_API_KEY. The server can start without that key, but tool calls require one. Logs are written to stderr.

Tools and capabilities

• Calculate natal, divisional, KP, Lal Kitab, Prashna, and Varshaphal charts.
• Build multiple Dasha timelines and correlate active periods with transits.
• Evaluate compatibility through several Indian matchmaking systems.
• Produce Panchanga days, monthly or festival data, Muhurta-related timings, Choghadiya, Hora, and Kaal intervals.
• Provide numerology, tarot, crystal, dream, angel-number, and astrology reference tools.

Limitations and notes

Accurate birth time matters for ascendants, houses, KP sub-lords, solar-return measures, and other time-sensitive results. Some tools use the current day or current instant unless a date and time are supplied. Panchanga locations require an IANA timezone alongside coordinates. The Asterwise MCP server is licensed under MIT.