Skip to main content
Glama
626,069 tools. Updated 2026-10-01 08:25

"Planet" matching MCP tools:

  • Get the turning points between two dates — dasha changes and slow-planet ingresses. This is the two-clocks view: the dasha sequence counted from birth (which theme is switched on) against gochara, the real sky on that date (the trigger). Use it for "what happens in the next five years", "when does this period change", "when does Saturn cross my Moon". get_dasha_periods answers when one clock changes; this answers when both point at the same thing. Every date is exact, bisected against the ephemeris to the day — not a sampled approximation. Args: chart_id: Handle returned by create_chart. The birth data is reused; the range below is independent of the chart's transit_date. start_date: YYYY-MM-DD, inclusive. end_date: YYYY-MM-DD, after start_date. systems: Dasha systems to include — vimshottari, yogini, ashtottari, chara_jaimini. Defaults to all four. Antardasha changes are reported for vimshottari only; the rest give mahadashas. types: Restrict to dasha_change, ingress and/or sade_sati. Defaults to all three. include_samples: Add a periodic strip showing the running dasha chain and Saturn/Jupiter position between the events. Off by default and capped at 13 rows, one year of months — for one date in full detail use get_transits. The event list is shorter when it is on. step: Spacing of that strip — month, quarter or year. Ignored unless include_samples is set. Returns the events, the natal anchors they are counted from, and the standing Sade Sati state at start_date. A range with more turning points than fit in one response is truncated **explicitly**, with the date to resume from — it is never silently shortened.
    ConnectorNo auth
  • Returns all crystals associated with a specific Vedic planet. Results are sorted with primary Navaratna gems first, then Uparatna substitutes. Only Navaratna and Uparatna Vedic assignments are returned — crystals with no Vedic planetary correspondence are excluded. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — identify the planet needing remediation. AFTER: asterwise_get_gemstone_recommendations — for chart-specific gem safety assessment. INPUT CONTRACT: planet: One of Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — natal chart house-lordship gem recommendation with contraindications; use for actual gem prescription, not just listing. asterwise_get_crystals — all 50 crystals including Western-only ones. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-by-planet/
    ConnectorOAuth
  • Returns a Vedic numerology reading from a date of birth alone: the mulank (root / psychic number, from the day of the month) and the bhagyank (destiny / life-path number, from the whole date), each with its ruling planet and traditional meaning, plus the classical lucky attributions -- numbers, colours, weekday, direction, gemstone. Optionally adds the Chaldean naam-ank when a name is supplied. Use this when the user asks about their number, life path or lucky colour/day/stone. It is NOT astrology and shares nothing with the chart tools: for a birth chart use get_janam_kundali, for a birth star use get_birth_details. Read-only deterministic arithmetic over the classical Chaldean number table -- no ephemeris is touched, and the result's Source line says so. No writes, no auth, at least 30 requests/min/IP per server instance. Birth time and place are not used, so none is asked for.
    ConnectorNo auth
  • Returns just the identity fields of a Vedic birth chart: the Moon's janma nakshatra (birth star) with its 1-27 number and pada, the janma rashi (moon sign) with its classical lord and the house it occupies, the lagna (ascendant) with degree in sign, nakshatra, pada and lord, and the navamsa (D9) lagna with its lord. Use this for the common single questions -- 'what is my nakshatra / rashi / lagna' -- and to fetch janma_nakshatra and janma_rashi values that get_muhurta_timings accepts. It returns NO planet table, no yogas and no dasha: for those call get_janam_kundali (whole chart) or get_dasha_periods (dasha only). Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa, whole-sign houses); no writes, no auth. Rate limits are counted per server instance: at least 30 requests/min/IP on this endpoint, plus a shared engine budget of at least 60/min/IP across all birth-chart tools.
    ConnectorNo auth
  • Create a serverless, standard, or stateful workload, or a scheduled job with type "cron" plus schedule (cron takes no autoscaling, timeoutSeconds, or debug). Containers go in containers[] and scaling in the autoscaling block. Set reachability in this call: public true or an explicit firewallConfig, otherwise nothing can reach it. Production defaults: readiness and liveness probes, CPU and memory sized to the runtime (the platform default is 50m and 128Mi), a metric matched to the traffic. Type and name are immutable. A standard HTTP app from an image, a repository, or files you wrote: deploy_app. A database: add_database, which also installs a Redis cache; other catalog products (queues, brokers, search, gateways): install_template.
    ConnectorOAuth
  • Read a build started by build_image: its status, its progress events, and its log. Statuses are queued and building (still running), pushed (done), and failed. The log comes back automatically when the build failed, since that is where the cause is; pass includeLog to see it otherwise. Pass waitSeconds to wait on the server until the build finishes.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to interact with the Planet API for satellite imagery ordering, subscriptions, and data management through natural language.
    17
    Apache 2.0

Matching MCP Connectors

  • Every environmental layer at one point on Earth

  • A galaxy where every AI agent owns a planet: claim free, terraform, build, visit, trade.

  • Return the exact object schema and REST API endpoints for a Control Plane resource kind, so you can author an accurate manifest for `cpln apply` or call the API directly. Call it before writing a `cpln apply` manifest, a CI/CD spec, or a REST body; never guess field names. Pick a `kind` and pass `org` (and `gvc` for workload/identity/volumeset). Large schemas come back as a shallow map with deep sections collapsed to {"_expand":"<path>"} stubs; pass `path` (e.g. "spec.containers") to expand a section on demand. Server-managed fields (id/status/version/etc.) are already removed; `name` and `kind` are required at create.
    ConnectorOAuth
  • Returns all crystals associated with a specific Vedic planet. Results are sorted with primary Navaratna gems first, then Uparatna substitutes. Only Navaratna and Uparatna Vedic assignments are returned — crystals with no Vedic planetary correspondence are excluded. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — identify the planet needing remediation. AFTER: asterwise_get_gemstone_recommendations — for chart-specific gem safety assessment. INPUT CONTRACT: planet: One of Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — natal chart house-lordship gem recommendation with contraindications; use for actual gem prescription, not just listing. asterwise_get_crystals — all 50 crystals including Western-only ones. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-by-planet/
    ConnectorOAuth
  • Reports which planets are retrograde on a date and — the part worth calling for — the two stations that OPEN AND CLOSE the period each body is in, so the answer is not "yes" but "since 2026-02-14, until 2026-03-07". Per body: the retrograde flag, ecliptic longitude, longitude speed, sign and degree, and both bracketing stations with exact UTC instants. Use it for Mercury retrograde, whether a planet is retrograde on a date, or when a period starts or ends. DELEGATE THIS RATHER THAN DERIVING IT: retrograde motion is apparent, not real, so the dates move every cycle, follow no rule and are not reliably memorised — Mercury alone turns three or four times a year and those dates get confidently misremembered by a week. A station is where longitude speed crosses zero, found by bisecting astronomy-engine's speed for eight bodies; expect it slower and dearer than the others here. DELIBERATELY EXCLUDED: the Sun and Moon, neither of which can station, and Rahu and Ketu, which move backwards every day of their existence. The "excluded" array gives the reasons; quote it rather than reporting an absence. CITATION: required. See server instructions.
    ConnectorNo auth
  • Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists. INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180, ayanamsa enum locally (Pydantic). Unknown birth time: omit time (a sunrise chart is cast and birth_time_provided=false); never pass time='00:00' for unknown, which is read as midnight. Lagna-sensitive results (houses, lagna, arudhas) are then approximate. DO NOT CONFUSE WITH: asterwise_get_divisional_chart — sixteen vargas only, not the primary radix bundle returned here. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-natal-chart/
    ConnectorOAuth
  • Computes KP ruling planets for the instantaneous chart at lat/lon with no birth data and returns day lord, Moon/Ascendant lord chains, and a deduplicated ruling_planets list. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards. INPUT CONTRACT: lat and lon only; no date parameter — "now" is implicit on the server clock. DO NOT CONFUSE WITH: asterwise_get_kp_chart — needs BirthData and returns full natal KP cusps. asterwise_get_prashna_chart — horary keyword workflow, not ruling-planet snapshot. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-kp-ruling-planets/
    ConnectorOAuth
  • Calculate a complete Western natal chart using the tropical zodiac and Swiss Ephemeris. Returns 10 planet positions with Placidus (or chosen) house placements, essential dignities, all active aspects, and element/modality/hemisphere balance statistics. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_western_transits_daily — layer current transits over this natal chart. AFTER: asterwise_get_western_synastry — compare this chart against a partner's chart. AFTER: asterwise_get_western_solar_return — annual return chart for the current year. INPUT CONTRACT: birth.date — YYYY-MM-DD. Example: '1985-11-12' birth.time — HH:MM (24-hour local time). Example: '06:45' birth.lat — Decimal degrees, north positive. Example: 19.076 (Mumbai) birth.lon — Decimal degrees, east positive. Example: 72.8777 (Mumbai) birth.timezone — IANA timezone string. Example: 'Asia/Kolkata', 'America/New_York', 'Europe/Rome', 'UTC'. Default: UTC. IMPORTANT: Timezone defaults to UTC — always supply the correct local timezone for accurate house cusps. An incorrect timezone shifts the Ascendant. birth.house_system — 'placidus' (default, most common), 'koch', 'equal', 'whole_sign'. Placidus is standard for most Western traditions. Whole sign is traditional/Hellenistic. NOTE: house_system is accepted here but silently ignored by transit, return, synastry, composite, and progression endpoints — those always use the birth location coordinates without house-system selection. ayanamsa — always tropical regardless of any value supplied; field is not present. DO NOT CONFUSE WITH: asterwise_get_natal_chart — Vedic sidereal chart using Lahiri ayanamsa; different zodiac, different house system, different planet set (9 grahas vs 10 tropical planets). asterwise_get_western_aspects — takes raw longitudes as input; use when you already have positions and don't need full chart computation. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-natal/
    ConnectorOAuth
  • Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations. INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint but uses a different engine (Atmakaraka + role-based prescription vs house lordship scoring); returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/
    ConnectorOAuth
  • Return precomputed astronomical events between start_date and end_date — any range within years -5000..+5000 (eclipses -1999..3000), instant. Events are global (location-independent) and served from binary-searched lookup tables — no live ephemeris computation. Example questions: "planetary events this month", "solar eclipses in the 12th century", "when was Shani retrograde in 1500 BCE?", "adhik maas years this decade". Ritu/ayana changes are Sayan sankrantis: Surya entering Meena=Vasanta, Vrishabha=Grishma, Karka=Varsha (=Dakshinayan start, = solstice), Kanya=Sharada, Vrishchika=Hemanta, Makara=Shishira (=Uttarayan start, = solstice) — query event_types=["sankranti"] with ayanamsa="Sayan". Args: start_date: Start date inclusive, YYYY-MM-DD (e.g. "2026-01-01"); negative years allowed (e.g. "-3101-01-01") end_date: End date inclusive, YYYY-MM-DD (e.g. "2026-12-31") ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical/Western) grah: Optional planet filter. One of: Surya, Chandra, Mangala, Budha, Guru, Shukra, Shani, Rahu, Ketu event_types: Optional list of event type filters. Valid values: "transit" – Mangala..Ketu change rashi (NOT Surya/Chandra) "sankranti" – Surya changes rashi (~monthly) "moon_transit" – Chandra changes rashi (~monthly) "full_moon" – Purnima (Moon at 180° elongation) "new_moon" – Amavasya (Moon at 0° elongation) "retrograde_start" – planet turns retrograde "retrograde_end" – planet resumes direct motion "equinox" – Vernal or Autumnal equinox (Sayan Surya) "solstice" – Summer or Winter solstice (Sayan Surya) "asta_start" – planet enters combust zone (Grah Asta) "asta_end" – planet exits combust zone (Uday) "solar_eclipse" – solar eclipse (catalog, years -1999..3000) "lunar_eclipse" – lunar eclipse (catalog, years -1999..3000) "kaal_sarp" – Kaal Sarp window (interval) "adhik_maas" – intercalary Hindu month (interval) "kshay_maas" – lost Hindu month (interval) "kumbh_mela" – Kumbh Mela window (interval) The max range is set by the densest requested type: 3 years by default, up to 1000 years for sparse-only queries (kumbh, maas). Interval events also carry end_time, duration_days, and type-specific details. Returns: Dict with keys: start_date, end_date, ayanamsa, count, events (list). Each event has: time (UTC ISO), event_type, grah, from, to, and (for intervals) end_time, duration_days, plus a details dict.
    ConnectorNo auth
  • Return a dasha (planetary period) timeline as a nested tree anchored on a date — past, present and future in ONE call. Works for BOTH planetary (graha) and sign (rasi) dasha systems; name the 'system' and the tool routes it automatically (default: vimsottari, anchored today, depth 3). Every period node has the same shape: 'level' (maha/antar/pratyantar/sookshma), 'ruler' (planet for graha, sign for rasi), 'start', 'end' (YYYY-MM-DD) and 'relation' (past/current/future). The result carries 'dasha_type' ('graha'/'rasi'), 'system', 'as_of', 'depth', a ready-made 'current' summary (with a 'path' and 'current_period_ends'), the full 'maha_timeline', and the expanded 'current_maha' → 'current_antar' → 'current_pratyantar' branches (rasi systems have two levels, no pratyantar; level 4 'sookshma' is graha-only). To drill into a SPECIFIC period regardless of date, pass 'maha' (and optionally 'antar') as a ruler name — it returns under 'selected_maha'/'selected_antar'. The full list of supported graha and rasi systems is the 'system' enum below. Set 'as_of_date' (YYYY-MM-DD, separate from birth 'date') to anchor on another time. Data only — no interpretation.
    ConnectorNo auth
  • Install a catalog template as a new release. Provide `name` (release name), `template`, optional `version` (defaults to latest), the `values` YAML (from get_template), and `gvc` unless the template creates its own. For postgres, mysql, mariadb, mongodb, or redis use add_database instead: it creates the credentials the template needs. A template that needs a secret created before install gets it from create_secret, never from values typed into the chat. dryRun true renders what would be created and applies nothing. Deployment is asynchronous: wait for it with get_installed_template and waitSeconds.
    ConnectorOAuth
  • Get Shadbala, Bhava Bala and Ishta/Kashta phala — how strong each planet and house is. Call this for "which planet is strongest", "is Saturn strong enough", or "which houses are weak". Shadbala is the six-fold Parasari strength; a planet meets expectation when `ratio` >= 1. Read `ratio` (>= 1 means the planet clears its own bar) and `rank_by_ratio` when saying a planet is strong or weak; the summary's `meets_requirement` lists every planet that qualifies. Each planet has its own `required_rupa`, so plain `rank` (absolute `total_rupa`) frequently disagrees: a planet can clear its own bar and still rank low overall. Use `strongest_by_ratio` / `weakest_by_ratio` for interpretation; the bare `strongest` / `weakest` keys are absolute-rupa based and kept only for backward compatibility. Args: chart_id: Handle returned by create_chart. detail: "summary" (default) gives totals, both ranks, ratio and Ishta/Kashta per planet. "full" adds the six sub-bala breakdowns and is several times larger — ask for it only when the components matter. Ishta phala is benefic capacity, Kashta phala malefic; they are derived from Shadbala, not independent measurements.
    ConnectorNo auth
  • Compute just a person's Vedic birth star (nakshatra) and core anchors. A one-shot shortcut: use this when the birth star is the whole question. If you expect follow-up questions about the same person's chart, prefer create_chart, which caches the full chart behind a reusable handle. Args: dob: Date of birth, YYYY-MM-DD (proleptic Gregorian). tob: Time of birth, HH:MM or HH:MM:SS, 24-hour. tz: IANA timezone name (e.g. "Asia/Kolkata") or fixed offset "+05:30". lat: Latitude in decimal degrees, North positive. lon: Longitude in decimal degrees, East positive. ayanamsha: Sidereal zero-point. Default lahiri. Returns the birth star (Moon's nakshatra), its pada and ruling planet, the Moon sign, the ascendant, and the Sun's nakshatra.
    ConnectorNo auth
  • Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists. INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180, ayanamsa enum locally (Pydantic). Unknown birth time: omit time (a sunrise chart is cast and birth_time_provided=false); never pass time='00:00' for unknown, which is read as midnight. Lagna-sensitive results (houses, lagna, arudhas) are then approximate. DO NOT CONFUSE WITH: asterwise_get_divisional_chart — sixteen vargas only, not the primary radix bundle returned here. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-natal-chart/
    ConnectorOAuth
  • Computes KP ruling planets for the instantaneous chart at lat/lon with no birth data and returns day lord, Moon/Ascendant lord chains, and a deduplicated ruling_planets list. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards. INPUT CONTRACT: lat and lon only; no date parameter — "now" is implicit on the server clock. DO NOT CONFUSE WITH: asterwise_get_kp_chart — needs BirthData and returns full natal KP cusps. asterwise_get_prashna_chart — horary keyword workflow, not ruling-planet snapshot. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-kp-ruling-planets/
    ConnectorOAuth
  • Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations. INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint but uses a different engine (Atmakaraka + role-based prescription vs house lordship scoring); returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/
    ConnectorOAuth