Astral Mcp

Astral MCP

Give your AI agent real astrology — natal charts, transits, synastry & moon phases.
Computed locally, cross-checked by two independent ephemerides. No API key, no account.

[npm version] [npm downloads] [License MIT] [Built for MCP]

[GitHub stars] [Precision audited] [Zero setup]

⚡ Zero-setup install. Wire it into Claude Desktop / Cursor / Hermes and call it immediately — no API key, no OAuth, no account: npx -y astral-mcp

A local-first MCP server that turns birth data into a full, precision-audited astrological reading for AI agents. Stateless and computational — nothing is stored, no credentials exist, and every tool but optional geocoding runs fully offline.

Astral MCP is Delx's focused astrology product. See the Delx platform map for its boundary with the separate Protocol, Security, Wellness and Commerce properties.

Built by David Mosiah. The astrology engine is ported from the Alkhemia app.

New to the protocol pattern? Read What Is an Astrology MCP Server? for the separation between deterministic chart computation and model interpretation, the recommended agent workflow, and the precision/privacy boundaries.

Ready to calculate one? Follow How to Generate a Natal Chart with MCP for the exact birthplace, timezone, unknown birth-time, payload and precision-audit workflow.

Handling sensitive inputs? Read How to Protect Birth Data in Astrology Agent Workflows for payload minimization, local computation, the optional OpenStreetMap boundary and the limits of privacy_mode=summary.

Why this exists

Most astrology libraries are fragile single-engine wrappers, and most "astrology APIs" want a key and a subscription. Agents need something they can trust and call instantly. Astral MCP does two things differently:

1. It just works. npx -y astral-mcp and you're calling charts — no OAuth, no account, no birthplace database to install.
2. It checks itself. Every natal chart is computed with one ephemeris and then independently re-derived, planet by planet, with a second one. If they disagree beyond a tight tolerance, the chart is flagged review instead of silently returning a wrong placement.

Setup in 60 seconds

Add it to your MCP client (Claude Desktop, Cursor, Hermes, …):

{  "mcpServers": {    "astral": {      "command": "npx",      "args": ["-y", "astral-mcp"]    }  }}

That's the whole setup. There is nothing to authenticate.

Run it directly if you want:

npx -y astral-mcp                      # stdio (default)ASTRAL_MCP_TRANSPORT=http npx -y astral-mcp   # streamable HTTP on 127.0.0.1:3000

See it before you connect

Call astral_demo for a fully-worked example chart (Greenwich, noon, Y2K) including its precision audit — no input, no network, no auth. It shows you the exact payload shape before you send real birth data.

Try it with your agent

"What's my natal chart? I was born 23 Feb 1989, 14:30, in Fortaleza, Brazil."

The agent calls astral_search_birthplace to resolve Fortaleza → lat/lon/timezone, then astral_compute_natal_chart.

"Any big transits hitting my chart this week?" → astral_current_transits "How compatible are we?" (two birth datas) → astral_synastry "What phase is the moon in today?" → astral_moon_phase

Precision

Astral MCP ships every natal chart with a precision audit. The primary engine (circular-natal-horoscope-js) computes the chart; the verifier (astronomy-engine) re-derives each planet's ecliptic longitude independently. A chart is verified only when every planet agrees within tolerance and lands in the same sign.

Across a built-in accuracy suite of charts spanning 1945–2010 and six timezones, the worst cross-engine disagreement is under 0.01°. Run it yourself:

npm run test:accuracy

Data availability

Tools

• astral_compute_natal_chart — full natal chart, precision-audited by default
• astral_current_transits — current + upcoming transits to a chart, with moon phase
• astral_synastry — compare two charts (harmony / chemistry / communication / growth)
• astral_moon_phase — moon phase, sign and illumination for any date
• astral_search_birthplace — geocode a place to latitude / longitude / timezone
• astral_demo — worked example chart, no input needed
• astral_capabilities — what this server supports and what it doesn't
• astral_data_inventory — data domains and recommended first calls
• astral_agent_manifest — install + usage rules for agents
• astral_connection_status — health check via a sample chart + dual-engine audit

The three chart tools (astral_compute_natal_chart, astral_current_transits, astral_synastry) take a privacy_mode parameter — a payload-verbosity axis separate from response_format:

• full (default) — the complete payload, including the per-planet precision audit
• structured — same structure, redundant/derivable fields dropped
• summary — only the high-signal essentials (luminaries + Ascendant, chart signature, top aspects)

A full Greenwich natal payload is ~6.9 KB; summary is ~1.2 KB (~80% smaller), so an agent that only needs a quick read can ask for less and spend fewer tokens.

Notes for accurate readings

• Pass the birthplace timezone, not the caller's. astral_search_birthplace returns it.
• birth_time is optional. Without it, noon is assumed: planet signs stay accurate, but the Ascendant and houses are unreliable.

Privacy & Security

Astral MCP stores nothing and holds no secrets. The only optional network call is astral_search_birthplace (OpenStreetMap), which sends just the place-name string you pass. See SECURITY.md.

Contributing

The computation core in src/engine/ is ported from Alkhemia — keep it framework-free. See AGENTS.md for the development rules and the test gate (npm test).

License

MIT — see LICENSE.

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y astral-mcp --http# GET  http://127.0.0.1:3000/health# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: ASTRAL_MCP_HOST, ASTRAL_MCP_PORT, ASTRAL_MCP_TRANSPORT=http.

Skill or MCP

npx -y astral-mcp call astral_connection_status --json '{}'