W8s Astro Mcp

io.github.w8sPublished by GitHub account w8sv0.15.2Updated Oct 24, 2026

Natal charts, transits, history, ingress forecasting, aspects, composite & Davison charts — SQLite.

VerifiedSTDIODesktop onlyDatabasesLocation & Lifestyle

Overview

AI-generated overview

A local astrology server that lets an assistant build natal, transit, event and relationship charts and store them in a queryable SQLite database.

What you can do
Create and manage astrological profiles for yourself, family and friends, with one set as owner by default. Calculate natal charts, transits, event and electional charts, and composite or Davison relationship charts. Compare charts and place today's sky in a chart's houses. Look up transit history by date, planet or sign, and forecast upcoming transits and ingresses. Generate an interactive placement dials page explaining planet, sign and house meanings.
When to use it
Useful if you want an assistant to keep a personal astrology database and answer questions about natal placements, daily transits, relationship synastry, auspicious timing, or past planetary positions without re-entering birth data each time.
Requirements
Runs locally over stdio. Needs Python 3.10+, uv (for uvx) or pip, and an MCP-compatible client such as Claude Desktop. Data is stored in a local SQLite file under the user's home directory. Optional high-precision ephemeris files can be downloaded.
Before you install
Stores birth dates, times and places for you and other people in a local database, so handle that personal data carefully. Chart data written by versions before v0.14 used local time as UT, giving wrong Ascendant, MC, houses and Moon; run the recalculation tool, which backs up the database before applying changes. The placement dials tool writes an HTML file to your Downloads folder.

Installation

In SourceWeft

  1. Open W8s Astro Mcp in the dashboard and add it to a workspace.
  2. 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

w8s-astro-mcp

Personal astrological MCP server — natal charts, transits, forecasting, and relationship charts backed by a queryable SQLite database.

[Tests] [PyPI version] [Python versions] [License: AGPL-3.0]

⚠ Upgrading from v0.12 or earlier? Your stored charts were calculated with the wrong time zone. Birth, event and electional times were treated as UT instead of local time, so the Ascendant, MC, houses and Moon were off. Planet signs almost always stay the same. Run w8s-astro-recalculate --all to see what changes, then add --apply. Details

Features

  • 🔭 Swiss Ephemeris precision — planetary positions via pysweph; optional high-precision file download
  • 🗂️ Multi-profile — manage charts for yourself, family, and friends
  • 📜 Persistent history — every transit lookup auto-logged to SQLite; query by date, planet, or sign
  • 🧭 Transit reading — compare today's sky to your natal chart with applying/separating direction and an estimated time of exactness; opt-in JSON output
  • 🎛️ Placement dials — an interactive page that teaches what a planet, a sign and a house mean, alone and together, using your own placements
  • 🔗 Relationship charts — composite and Davison charts for any group of 2+ people; place today's sky in any chart's house system
  • 🗓️ Event & electional tools — cast charts for any moment; scan windows for auspicious times

Quick Start

1. Install uv if you don't have it — see the uv installation guide for your platform.

2. Add to your Claude Desktop config:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
json
{  "mcpServers": {    "w8s-astro-mcp": {      "command": "uvx",      "args": ["w8s-astro-mcp"]    }  }}

3. Restart Claude Desktop, then create your profile:

"Create an astro profile for me — my name is [Name], born [YYYY-MM-DD] at [HH:MM] in [City, State]."

4. Set yourself as the owner:

"Set me as the owner profile."

This tells the server who you are. All tools default to your chart unless you ask about someone else. Everything is stored in ~/.w8s-astro-mcp/astro.db (macOS/Linux) or %USERPROFILE%\.w8s-astro-mcp\astro.db (Windows).

Installation

Recommended: uvx (no install required)

uvx pulls the package from PyPI and runs it in an isolated environment automatically. Use the config above.

Alternative: pip

bash
pip install w8s-astro-mcp

Then use "command": "w8s-astro-mcp" (no args) in your Claude Desktop config.

Upgrading from an earlier version

If you have an existing database from before v0.12, run the migration script once:

bash
python scripts/migrate_owner_profile.py

This renames the internal current_profile_id column to owner_profile_id. Safe to run multiple times.

Upgrading to v0.14.0 — recalculate your stored charts. Earlier versions used the local birth time as if it were UT, so every stored natal chart has the wrong Ascendant, MC, houses and Moon. Fix it once after upgrading:

bash
w8s-astro-recalculate --all            # dry run: shows exactly what would changew8s-astro-recalculate --all --apply    # backs up the database first, then recalculates# with uvx: uvx --from w8s-astro-mcp w8s-astro-recalculate --all

Add --events to include saved event charts, or --event LABEL to recalculate just one (repeat it for several). It is safe to run more than once, and your AI assistant will mention it after you upgrade if any stored chart still needs recalculating. The compare_charts changes in this release are additive: it keeps its existing output and adds one line per aspect (see the CHANGELOG if you parse that text). If you would rather not be reminded, ask it to dismiss the notice. A note on times: birth time, event time and electional dates are local times (converted using the location's timezone); the time you pass to get_transits, find_house_placements and compare_charts is UT.

If a new install fails with AttributeError: 'Server' object has no attribute 'list_tools': upgrade to v0.12.1 or later (uvx --refresh w8s-astro-mcp, or pip install -U w8s-astro-mcp). Earlier versions did not limit which MCP SDK version they accept, so a new install picked up SDK 2.x, which this server does not support yet.

Requirements

  • Python 3.10+
  • uv (for uvx method) or pip
  • Claude Desktop (or any MCP-compatible client)

Use Cases

Get started:

"Create an astro profile for me — my name is [Name], born [YYYY-MM-DD] at [HH:MM] in [City, State]."

"Show me my natal chart."

Daily practice:

"What are my transits for today?"

"When was Mercury last retrograde?"

"What major transits are coming up in the next 90 days?"

"Which of today's transits to my chart are building and which are fading?"

Learn what a placement means:

"Make me a placement dials page so I can see what Mars in Taurus in House 3 means." (saves an HTML file to your Downloads folder; open it in a browser)

Other profiles:

"Show me Liz's natal chart."

"What are her transits today?"

"Compare my chart with Liz's." (synastry)

House placements:

"Where are today's planets in my natal houses?"

"Where does today's sky fall in our composite chart?"

Relationships:

"Create a profile for my partner, born [YYYY-MM-DD] at [HH:MM] in [City, State]."

"Create a connection called 'Us' and show me our synastry."

"Calculate a Davison chart for us."

Events & planning:

"Cast a chart for the moment we got married — [date] at [time] in [city]."

"Find auspicious times to sign a contract next month — Moon not void, Mercury direct."

History & research:

"When was Jupiter last in Taurus?"

"Show me all my transit lookups from last month."

Documentation

DocContents
docs/ARCHITECTURE.mdDirectory structure, full tool list, data flow, design decisions
docs/DATABASE_SCHEMA.mdFull ERD, all models, example SQL queries
docs/ROADMAP.mdPhase history and planned work
docs/TESTING_MCP.mdHow to configure Claude Desktop and smoke-test the server

Contributing & Development

See AGENTS.md for the development workflow, testing commands, branch strategy, and release checklist.

Questions & Bugs

Open an issue on GitHub.

License

AGPL-3.0

Source: README.md at commit 74ab1a3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

6
  1. v0.15.2LatestOct 11, 2026
  2. v0.15.1Oct 11, 2026
  3. v0.15.0Oct 11, 2026
  4. v0.14.0Sep 20, 2026
  5. v0.12.1Sep 20, 2026
  6. v0.12.0Sep 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.