
Auseklis Astrology
io.github.igmizoPublished by GitHub account igmizov0.4.0Updated Nov 10, 2026
Astrology from a real ephemeris: natal charts, transits, synastry, eclipses, returns. No API keys.
Overview
Astrology MCP server that computes natal charts, transits, synastry, returns and eclipses from a real local ephemeris, so assistants stop guessing planet…
- What you can do
- Compute positions and charts: single body positions, full natal charts with houses and aspects, progressions, synastry and composite charts
- Analyze transits: aspects from the current or any sky to a natal chart, and the exact moment an aspect perfects
- Find timed events: solar, lunar and planetary returns, retrograde stations, sign ingresses, moon phases and eclipses with local visibility
- Apply chart settings: IANA timezones with historical DST, tropical or sidereal zodiacs, several house systems, nodes and Lilith
- Use built-in prompts for a natal chart reading or current sky report, plus a glossary resource
- When to use it
- Useful when you want an assistant to produce astrological charts and event timings from real ephemeris math rather than invented positions, for example a birth chart, a Saturn return date, or Mercury retrograde periods in a given year.
- Requirements
- Runs locally over stdio, typically via npx with Node.js; no API keys or configuration. A self-hosted Cloudflare Worker deployment is also described, optionally protected by the MCP_SHARED_SECRET bearer token. The model must supply coordinates, since the server only converts local time to UTC.
Installation
In SourceWeft
- Open Auseklis Astrology 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
auseklis
Astrology MCP server — natal charts, transits, synastry, progressions, returns, eclipses, retrogrades, moon phases. Computed from a real ephemeris, so AI agents stop hallucinating planet positions.
Named after the Latvian morning star. MIT-licensed with no AGPL ephemeris data — see Licensing.
Tools
Plus two prompts (natal_chart_reading, current_sky_report) and a glossary resource (auseklis://glossary).
Features: local birth times with IANA timezones (full historical DST handling) · tropical and sidereal (Lahiri, Fagan/Bradley) zodiacs · whole-sign, equal, Porphyry, and Placidus houses · mean lunar nodes and Black Moon Lilith · Part of Fortune (classical day/night formula).
Installation
Claude Code
Claude Desktop / any MCP client (stdio)
No API keys, no configuration — the ephemeris is computed locally.
Desktop Extension
Download auseklis.mcpb from the releases page and double-click to install in Claude Desktop. Or build it yourself: npm run bundle.
Remote (self-hosted)
The same server runs as a Cloudflare Worker speaking Streamable HTTP. Deploy it to your own account:
Set the MCP_SHARED_SECRET secret to require a bearer token.
Library usage
The ephemeris core (everything under src/ephemeris/) is importable directly — no MCP client or subprocess needed. This is the right shape for serverless runtimes (Vercel, Workers), where spawning npx auseklis per request is not an option:
auseklis/ephemeris carries the chart math (natal, transits, synastry, composite, progressions, single positions, angles) plus resolveInstant for local-time → UTC conversion; …/events and …/eclipses carry the time-domain searches. Fully typed, ESM only, no data files.
Example questions to ask
- "Compute my natal chart — born 15 March 1990, 15:45 in Riga."
- "What's transiting my Sun this month?"
- "When exactly is my Saturn return?"
- "Synastry between me and my partner?" (two birth date/times)
- "When is Mercury retrograde in 2027, and in which signs?"
- "Is tonight's full moon visible as an eclipse from here?"
The model handles place-name → coordinates; the server handles local-time → UTC via the IANA timezone database.
Accuracy
Positions come from astronomy-engine (VSOP87 + NOVAS C 3.1): ±1 arcminute for 1700–2200, far below the 1° resolution astrological interpretation uses. Event searches (stations, ingresses, returns, quarters) are refined to ~1 second of time. Verified in CI against published eclipse dates, the 2026 equinox, NOVAS Sun positions, and an independent Placidus implementation.
Architecture
The EphemerisBackend interface in engine.ts is the deliberate swap seam: a future Rust/WASM clean-room ephemeris only needs to reimplement that one interface.
Development
See docs/tools.md for the full tool reference and docs/architecture.md for design notes.
Licensing
MIT. This project deliberately avoids the Swiss Ephemeris (.se1/.se2 data files and the sweph bindings): those are AGPL-licensed, which would impose AGPL obligations on any network service built on them. Everything here is computed from MIT-licensed code with no external data files — safe to embed, fork, and deploy commercially. Details in NOTICE.
The trade-off: no Chiron or asteroids (they need ephemeris data files). They are on the roadmap via public-domain JPL-derived data.
Roadmap
- v1: Rust/WASM clean-room ephemeris backend behind the same
EphemerisBackendseam - Chiron + major asteroids from public-domain JPL data
- Koch houses, declination/parallel aspects
Source: README.md at commit 57e6417
Tools
0Version history
1- v0.4.0LatestSep 16, 2026
Score
50% 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