MCP Tool Catalog
7 tools. One protocol.
Every Vedākṣha computation is available as an MCP tool with a complete JSON schema. Your AI agent discovers the tools, reads their schemas, and calls them — no custom integration code required.
compute_natal_chartComputes a complete natal (birth) chart including planetary positions, house cusps, nakshatras, aspects, dignities, and yogas.
Input Parameters
julian_dayf64Julian Day number for the moment of birthlatitudef64Geographic latitude in decimal degreeslongitudef64Geographic longitude in decimal degreesayanamshaAyanamshaSidereal zodiac system (e.g., Lahiri, Fagan-Bradley)house_systemHouseSystemHouse division method (e.g., Placidus, WholeSign)Returns
ChartGraph — a property graph with planetary nodes, house nodes, sign nodes, and typed edges representing aspects, placements, and dignities. Includes chart_highlights ranked by significance.
How an AI Agent Uses This
A user says: "What does my birth chart look like?" The agent converts the birth datetime to a Julian Day, calls compute_natal_chart, and receives a fully structured chart. It reads chart_highlights to summarize the most significant features, and uses nl_description fields for natural language output.
compute_dashaComputes a Vedic dasha (planetary period) timeline with up to 5 levels of sub-periods.
Input Parameters
julian_dayf64Julian Day number for the birth momentmoon_longitudef64Sidereal longitude of the Moon at birthdasha_systemDashaSystemVimshottari, Yogini, or Charalevelsu8Depth of sub-periods (1-5)Returns
DashaTree — a hierarchical tree of planetary periods with start/end dates, ruling planet, and nl_description for each node.
How an AI Agent Uses This
A user asks: "What planetary period am I in?" The agent computes the dasha tree, finds the current date within the hierarchy, and reports the active Mahadasha, Antardasha, and Pratyantardasha with their ruling planets and interpretive descriptions.
compute_vargasComputes any of the 16 Shodasha Varga divisional charts used in Vedic astrology.
Input Parameters
julian_dayf64Julian Day numberlatitudef64Geographic latitudelongitudef64Geographic longitudevargaVargaDivisional chart type (D1 through D60)ayanamshaAyanamshaSidereal zodiac systemReturns
ChartGraph — the divisional chart as a property graph, with planetary positions recalculated for the selected harmonic division.
How an AI Agent Uses This
A user asks: "Show me my Navamsha chart." The agent calls compute_vargas with Varga::D9 to get the ninth-harmonic divisional chart, which reveals partnership and dharmic patterns.
emit_graphConverts a ChartGraph into a database-ready or embedding-ready format.
Input Parameters
chart_graphChartGraphThe chart graph to emitformatEmitFormatCypher, SurrealQL, JsonLd, Json, or EmbeddingTextReturns
String — the chart serialized in the requested format. Cypher produces CREATE statements for Neo4j. SurrealQL produces INSERT statements. JSON-LD produces linked data. EmbeddingText produces optimized chunks for vector stores.
How an AI Agent Uses This
An agent building a knowledge graph calls emit_graph with EmitFormat::Cypher after computing a chart, then executes the resulting Cypher statements against a Neo4j database. Later, it queries the graph to find cross-chart patterns.
compute_transitComputes planetary positions for a given moment — used for current sky, progressions, or transit overlays.
Input Parameters
julian_dayf64Julian Day number for the transit momentayanamshaAyanamshaSidereal zodiac systemReturns
TransitSnapshot — planetary positions at the specified moment, with sign, nakshatra, and degree for each body.
How an AI Agent Uses This
A user asks: "Where are the planets right now?" The agent converts the current UTC time to a Julian Day and calls compute_transit. It can then overlay these positions on the user’s natal chart to identify active transits.
search_transitsSearches for exact transit events within a date range — conjunctions, sign ingresses, retrograde stations, and aspect formations.
Input Parameters
start_jdf64Start of the search window (Julian Day)end_jdf64End of the search window (Julian Day)bodiesVec<Body>Which planets to trackevent_typesVec<TransitEventType>Types of events to findayanamshaAyanamshaSidereal zodiac systemReturns
Stream<TransitEvent> — a streaming sequence of transit events, each with exact Julian Day, involved bodies, event type, and nl_description.
How an AI Agent Uses This
A user asks: "When does Jupiter enter Taurus?" The agent searches for SignIngress events for Body::Jupiter in the relevant date range. Results stream back as they are found, so the agent can report the first match immediately.
search_muhurtaFinds auspicious time windows based on Vedic electional criteria — nakshatra, tithi, yoga, karana, and custom scoring rules.
Input Parameters
start_jdf64Start of the search window (Julian Day)end_jdf64End of the search window (Julian Day)latitudef64Geographic latitudelongitudef64Geographic longitudecriteriaMuhurtaCriteriaScoring rules for auspiciousnessReturns
Vec<MuhurtaWindow> — ranked time windows with scores, active nakshatra, tithi, yoga, and karana for each window.
How an AI Agent Uses This
A user asks: "When is a good time to start a business this month?" The agent calls search_muhurta with criteria favoring nakshatras associated with new ventures, and returns the top-ranked windows with explanations.
Ready to connect?
See the quickstart guide to wire up your agent in 5 minutes.