An open engine needs open builders.
Birthstar MCP is a Vedic astrology engine that agents can call — thirty tools over the Swiss Ephemeris, all free to call. The engine is further along than the things built on it, which is where you come in.
Six things that would actually help
Each of these names a real gap, not a generic invitation.
Tell us what to build
The fastest contribution. If you can describe the app, we can tell you which of the thirty tools it needs — and whether the engine can already do it.
Work on the engine
Python over the Swiss Ephemeris, with a strict rule: nothing is faked. An unimplemented quantity returns null with a reason, never an invented number.
Contribute a verified chart
The suite validates against one reference chart. More independently-verified charts — ideally computed by a practising astrologer against a known birth time — would catch regressions nothing else can.
Add to the prompt library
Twelve workflows ship as native MCP prompts. A good addition chains at least two tools, asks in plain language, and never puts an astrological claim in the model’s mouth.
Break it and say how
Errors are returned, not raised — so a wrong answer is worse than a crash. If a tool returns something that looks plausible and is not, that is the highest-value bug report you can file.
Explain the hard parts
Ayanamsha choice, whole-sign versus Placidus, why a Vedic sign differs from a Western one. The engine documents its methods; the explanations for newcomers are thinner.
What would you build?
It goes straight to the project tracker. Half a sentence is enough — if the engine can already do it, we will tell you which tools to call.
Prefer to just start?
You do not need permission or an account. Point any MCP client at the endpoint and build something — the developer page has six paste-and-run app blueprints to start from.