
Astro
io.github.aryaminusPublished by GitHub account aryaminusv2.4.0Updated Oct 24, 2026
Multi-tradition astrology. 19 modes, 18 tools. Deterministic ephemeris engine.
Overview
A local astrology engine that computes real birth charts, transits and synastry across Western, Vedic and Chinese BaZi traditions for the assistant to interpret
- What you can do
- Compute natal charts, transits, returns, progressions and planetary hours from birth data and location coordinates, with aspect patterns, Arabic parts and fixed stars included by default across 19 modes and 18 tools. Compare two charts for synastry, compatibility and composite readings, with a 0–100 score. Produce Vedic divisional charts, panchang and dasha-style material, and Chinese BaZi four-pillar output. Map locations with astrocartography and pick dates or times with electional and panchang tools. Return structured JSON the model interprets against bundled classical rulesets rather than guessing positions.
- When to use it
- Useful when you want an assistant to answer astrology questions from computed planetary positions instead of invented ones: natal readings, relationship compatibility, timing questions, auspicious dates, or relocation and career-location analysis.
- Requirements
- Runs as a local process on the desktop. The engine is pure Python with no dependencies, so a Python 3 interpreter is needed; the README also offers install through a skills CLI, a packaged release, or a git clone. Birth date, latitude, longitude and an IANA time zone are required input; time of birth is optional. A public remote endpoint is mentioned as an alternative.
Installation
In SourceWeft
- Open Astro in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Astro — Multi-Tradition Astrology Engine for AI Agents
Trustworthy birth charts, transits, and synastry across Western, Vedic/Jyotish, and Chinese BaZi. The engine computes; the model interprets.
[MIT] [Python 3.10+] [MCP] [REST] [Deploy] [smithery badge]
Paste this into any AI chat or agent (Claude, ChatGPT, Gemini, Claude Code, Cursor, Codex, DeepSeek, Perplexity…). It installs Astro itself — you don't set anything up first:
Local install — works on Claude Code, Cursor, Codex, Copilot, Gemini CLI, and 50+ Agent Skills hosts:
Why this exists
A raw LLM cannot tell you where Mars was on a Tuesday in 1997 — it hallucinates chart data. Astro splits the work:
- Engine — deterministic Python math computes real sky positions (zero deps, pure stdlib)
- Skill — orchestrates the engine + loads classical interpretation rulesets
- Glue — MCP, REST, CLI, ChatGPT Actions reach the engine from any platform
The model never guesses a position. It interprets structured output grounded in 8 classical rulesets.
19 modes · 3 traditions · zero dependencies
Modes: natal, transit, synastry, compatibility, composite, astrocartography, horary, event, solar/lunar/planetary return, navamsa, varga (D2–D60), panchang, moon phase, numerology, progressions, planetary hours, transit-to-natal aspects. Full list and parameters in skills/astrology/SKILL.md.
Traditions: Western tropical, Vedic/Jyotisha (Lahiri sidereal), Chinese BaZi + Tibetan/Buddhist.
Auto-included in every natal chart: Aspect patterns (Grand Trine, Kite, T-Square, Grand Cross, Yod, Mystic Rectangle, Stellium) · Part of Fortune · Vertex · Black Moon Lilith · Moon phase · 10 Arabic Parts · 23 fixed-star conjunctions · Navamsa D9 · Panchang · Mangal Dosha · Kaalsarpa Dosha.
Try it
After installing, ask any of these:
- "What's my chart?" → full natal
- "Am I compatible with…?" → synastry + 0–100 scoring
- "When's my Saturn return?" → planetary return + timing
- "Where should I live for career?" → astrocartography
- "What time should I start the meeting?" → Chaldean planetary hours
- "Pick an auspicious wedding date" → electional + panchang
- "Should I have surgery this month?" → medical timing
- "What does today have in store?" → transits + natal aspects
Project layout
Cloud hosting
Free by default. No auth, no rate limits. Set ASTRO_API_KEY to gate, ASTRO_RATE_LIMIT to throttle.
Render (one-click, free tier): Connect this repo → New → Blueprint. render.yaml provisions everything. Verify with curl https://astro-api-a2rc.onrender.com/health. Free tier spins down after 15 min idle; first request after idle takes ~30s.
Docker:
Raw Python:
MCP SSE (Smithery, Cloudflare, Poke):
Cloud MCP SSE (no deploy needed): https://astro-api-a2rc.onrender.com/mcp/sse — free Render instance. ~30s cold start.
Env vars and operational endpoints documented in AGENTS.md.
Documentation
Contributing
PRs welcome. Hard rules: engine stays zero-dep, engine never imports frameworks, touch all 4 surfaces (engine + MCP + REST + OpenAPI), the skill is honest. See CONTRIBUTING.md.
License
MIT. Reference texts in skills/astrology/references/ are original MIT-licensed syntheses of classical sources.
Source: README.md at commit 82df4c1
Tools
0Version history
1- v2.4.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.