VedaVisor Vedic Astrology MCP

io.github.dchhillPublished by GitHub account dchhillv1.0.0Updated Oct 25, 2026

Professional Vedic astrology tools for AI agents via MCP.

The publisher's own server: Visor

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP server giving AI assistants professional Vedic astrology tools, accessed with a VedaVisor API key.

What you can do
Provides Vedic astrology capabilities to an AI assistant through a hosted remote endpoint. The registry description calls them professional Vedic astrology tools for AI agents. No individual tools are listed in the supplied material, so the exact functions are not documented here.
When to use it
When you want an assistant to work with Vedic astrology content and you already have or plan to get a VedaVisor MCP API key.
Requirements
A remote endpoint at mcp.vedavisor.com over streamable HTTP. A required bearer token sent in the Authorization header, using a VedaVisor MCP API key. Network access to the endpoint.
Before you install
The server requires an API key sent as a bearer token in the Authorization header; keep that key private and send it only to this endpoint. No tools are listed, so what the server can read or change is not documented here.

Installation

In SourceWeft

  1. Open VedaVisor Vedic Astrology MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.dchhill%2Fvedavisor-vedic-astrology-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vedavisor-vedic-astrology": {
      "type": "http",
      "url": "https://mcp.vedavisor.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

22

calculate_birth_chart

Calculate a complete Vedic birth chart (Kundli) with high-precision sidereal positions. WHEN TO USE: When an agent needs someone's Vedic chart to analyze planets, houses, nakshatras, yogas, or as the basis for dashas and predictions. WHAT IT DOES: Computes sidereal (Lahiri) planetary longitudes, house cusps, ascendant, and the Moon's nakshatra using a professional-grade Vedic calculation engine. RETURNS: JSON with planets (sign, house, degree), houses, ascendant, moon_nakshatra, and lagna_lord. NEXT: Pass the chart to calculate_vimsottari_dasha or ask_cosmic_advisor.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetimezone_offset

calculate_daily_panchanga

Calculate Panchanga factors for a date and location. WHEN TO USE: When an agent needs the tithi, nakshatra, yoga, karana, and weekday context for planning or interpreting a date. WHAT IT DOES: Computes traditional daily Vedic calendar factors for the supplied location and timezone offset. RETURNS: JSON with tithi, nakshatra, yoga, karana, weekday, and related timing data including muhurat windows and choghadiya divisions. NEXT: Use calculate_birth_chart for person-specific interpretation.

Parametersdayrequiredhouryearrequiredmonthrequiredlatitudelongitudeayanamsa_modetimezone_offset

get_daily_rashifal

Get the daily Vedic horoscope (Rashifal) for a zodiac sign — sign-based, not personalized. WHEN TO USE: When a user or agent wants today's prediction for a specific rashi (Moon sign). Note: this is a sign-based rashifal, not a personalized chart-aware horoscope. For in-depth, chart-specific daily guidance that reads your full natal chart and current transits, use daily_horoscope (Pro tier). For basic sign-level predictions, this works. WHAT IT DOES: Returns the cached daily rashifal text for the requested sign. RETURNS: JSON with sign name, date, and rashifal content. NEXT: Use calculate_birth_chart to find the user's Moon sign first if they do not know it.

Parameterssign_namerequired

calculate_full_numerology

Calculate a full numerology profile from name and birth date. WHEN TO USE: When an agent needs Chaldean name numerology plus DOB-based radical and destiny numbers with life-aspect scores. WHAT IT DOES: Combines Chaldean name number, radical number (from day), destiny number (from full date), governing planet for each, and 0-100 scores across 10 life domains (finance, career, romance, health, etc.). RETURNS: JSON with name_number, radical_number, destiny_number, planet assignments for each, traits, and the life_aspects score map.

Parametersdaynameyearmonth

calculate_vimsottari_dasha

Calculate the Vimsottari Mahadasha sequence and current period. WHEN TO USE: When an agent needs to know what planetary period a person is currently running and upcoming periods. WHAT IT DOES: Computes the full 120-year Vimsottari dasha timeline from the Moon's nakshatra at birth, with sub-periods (antardashas) for the current mahadasha. RETURNS: JSON with current mahadasha, antardasha, start/end dates, and the full sequence. NEXT: Use calculate_birth_chart for the foundational chart.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetimezone_offset

resolve_place

Resolve a place name to geo-coordinates and timezone. WHEN TO USE: When an agent has a city or place name but needs latitude, longitude, and timezone offset for chart calculations. WHAT IT DOES: Geocodes the query via OpenStreetMap Nominatim and returns matching places with display name, coordinates, and country. RETURNS: JSON list of places with display_name, lat, lon, country, and timezone_offset (where available). NEXT: Use the returned coordinates with calculate_birth_chart.

Parameterslimitqueryrequired

get_weekly_transit_events

Get this week's major planetary transit events (sign/nakshatra ingresses, stations). WHEN TO USE: When an agent needs to know what transits are happening this week for context in predictions or planning. WHAT IT DOES: Detects sign ingresses, nakshatra ingresses, and retrograde/ direct stations for all nine planets over the current or requested week. RETURNS: JSON with iso_week, week_start, week_end, and a list of transit events each with planet, type, from/to signs, timestamp, and severity. NEXT: Use calculate_birth_chart to see how these transits aspect the natal chart.

Parametersdayyearmonthiso_weekayanamsa_mode

find_auspicious_times

Find favorable Muhurta windows for a task. WHEN TO USE: When an agent needs the best dates or time windows to start an activity (marriage, travel, business, property, education, medical). WHAT IT DOES: Scores each day in the range using Panchanga factors and task-specific nakshatra rules, ranking results by auspiciousness. RETURNS: JSON list of windows ranked by score (0-100) with nakshatra, tithi, weekday, and reasoning factors for each. NEXT: Use ask_cosmic_advisor to interpret the top window for the user.

Parametersend_daterequiredlatituderequiredlongituderequiredtask_typerequiredstart_daterequiredtimezone_offset

calculate_yogas

Calculate planetary yogas in a birth chart. WHEN TO USE: When an agent needs to know which classical yogas (planetary combinations) are present, such as Pancha Mahapurusha yogas, Raja yogas, and Dhana yogas. WHAT IT DOES: Computes yogas from D-1 planetary positions including special lagnas. RETURNS: JSON list of yoga results with names and descriptions. NEXT: Use ask_cosmic_advisor for interpretation of the yogas.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetimezone_offset

calculate_compatibility

Calculate Vedic compatibility (Kundli matching) between two people. WHEN TO USE: When an agent needs to evaluate relationship compatibility using Ashtakoota (Guna Milan) and other classical matching factors. WHAT IT DOES: Computes full compatibility scores from both birth charts including Ashtakoota points, Manglik dosha, and Nadi matching. RETURNS: JSON with total score, Ashtakoota breakdown, dosha analysis, and key strengths and watch-outs.

Parametersday1requiredday2requiredlat1requiredlat2requiredlon1requiredlon2requiredhour1requiredhour2requiredyear1requiredyear2requiredmonth1requiredmonth2required+3 more

calculate_ashtakavarga

Calculate Ashtakavarga (eight-fold strength) tables. WHEN TO USE: When an agent needs the bhinna-ashtakavarga and sarva- ashtakavarga bindus for transit analysis and planetary strength. WHAT IT DOES: Computes the full Ashtakavarga system including individual planet contributions and combined house totals. RETURNS: JSON with bindus per planet per house and the sarva totals.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetimezone_offset

recommend_remedies

Recommend Vedic remedies from a birth chart. WHEN TO USE: When an agent's user is asking about remedies for planetary afflictions or life challenges and has birth details available. WHAT IT DOES: Computes the chart, identifies weak or afflicted planets, and returns deterministic recommendations such as mantras, gemstones, rituals, and charitable acts. RETURNS: JSON with mantras, rudraksha, puja, gemstones, weak planets, and strength summary.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetimezone_offset

calculate_varga_charts

Calculate divisional (Varga) charts for a birth chart. WHEN TO USE: When an agent needs detailed divisional charts beyond D-1, such as Navamsa (D-9) for relationships and Dasamsa (D-10) for career. Specify varga_list as a comma-separated string of D-N names (e.g., "D-1,D-2,D-3,D-7,D-9,D-10,D-12,D-16,D-20,D-24,D-27,D-30,D-40,D-45,D-60"). WHAT IT DOES: Computes the requested divisional charts from the birth positions using classical Vedic varga rules. RETURNS: JSON mapping each requested varga name to its planetary positions.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudevarga_listtimezone_offset

calculate_all_dashas

Calculate all applicable dasha systems for a birth chart. WHEN TO USE: When an agent needs a comprehensive dasha analysis beyond Vimsottari — including Ashtottari, Kalachakra, Narayana, Shoola, and other conditional dasha systems. WHAT IT DOES: Computes the birth chart, detects which dasha systems apply, and returns the current period for each applicable system. RETURNS: JSON mapping dasha system names to their current period, start/ end dates, and sub-periods at the requested depth. NEXT: Use calculate_birth_chart first if you only need Vimsottari dasha.

Parametersdayrequiredhourrequiredyearrequireddepthmonthrequiredminutelatitudelongitudetimezone_offset

calculate_transits

Calculate current planetary transit positions for a date. WHEN TO USE: When an agent needs to know where planets are right now (or on a specific date) for transit analysis, gochara, or mundane astrology. WHAT IT DOES: Computes sidereal longitudes, nakshatras, signs, houses, and retrograde status for all nine planets at the given date and location. RETURNS: JSON with transit_date, planetary positions (sign, house, degree, nakshatra, pada, retrograde flag), and the ascendant for the moment.

Parametersdayrequiredhouryearrequiredmonthrequiredlatitudelongitudeayanamsa_modetimezone_offset

calculate_tajaka

Calculate the annual Tajaka solar return chart and aspects. WHEN TO USE: When an agent needs the Varshaphala (annual solar return) chart, Muntha, and Tajaka aspects for yearly predictions. WHAT IT DOES: Computes the solar return chart for the target year, casts Tajaka (harmonic) aspects between planets, and calculates Muntha position. RETURNS: JSON with solar_return_chart, tajaka_aspects, muntha (sign, house, lord), target_year, and completed_years. NEXT: Use calculate_varshaphala for the full predictive report, or ask_cosmic_advisor for interpretation.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetarget_yeartimezone_offset

ask_prashna

Answer a Prashna (horary) question using a moment chart. WHEN TO USE: When a user asks a focused yes/no/maybe question and wants horary astrological guidance. WHAT IT DOES: Casts a chart for the question moment, maps the domain, and returns a deterministic verdict with confidence and factors. RETURNS: JSON with verdict (yes/no/maybe), confidence (0-100), domain, house analyzed, reasoning, and chart factors.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredlatituderequiredquestionrequiredlongituderequiredtimezone_offset

calculate_karakas

Calculate Chara and Sthira Karakas (significators). WHEN TO USE: When an agent needs to identify the key planetary significators in a chart for specific life areas. WHAT IT DOES: Computes Chara Karakas (variable significators based on planetary degrees) and Sthira Karakas (fixed significators). RETURNS: JSON with Atmakaraka, Amatyakaraka, and other karaka assignments.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudetimezone_offset

calculate_varshaphala

Calculate the full Varshaphala (annual prediction) report. WHEN TO USE: When an agent needs a comprehensive annual forecast for a person including solar return chart, Muntha, Varshesha, Mudda dasha, Sahams, Tajaka yogas, and month-by-month outlook. WHAT IT DOES: Runs the full Vedic annual prediction pipeline — computes the solar return chart, determines the year lord (Varshesha), the Muntha progression, Panchadhikari (five office-bearers), Mudda (annual) dasha periods, sensitive points (Sahams), Tajaka yogas, and a month-by-month transit summary. RETURNS: JSON with all Varshaphala sections: solar_return_chart, varshesha, muntha, panchadhikari, mudda_dasha, sahams, tajaka_yogas, monthly_outlook, and is_day_chart.

Parametersbirth_dayrequiredbirth_latbirth_lontz_offsetbirth_hourrequiredbirth_yearrequiredbirth_monthrequiredtarget_yearrequiredbirth_minutehouse_systemayanamsa_mode

daily_horoscope

Generate a personalized daily horoscope from a birth chart — AI-powered, not template-based. WHEN TO USE: When an agent's user wants a chart-aware daily prediction based on their birth chart, current transits, and dasha period. Unlike basic rashifal services that return the same generic paragraph for everyone with the same Moon sign, this tool reads the full natal chart and current planetary transits to produce guidance unique to that person. WHAT IT DOES: Computes the birth chart, builds a prompt with full chart context in a warm Vedic astrologer voice, and generates a personalized 3-4 paragraph daily guidance message grounded in classical Jyotish. RETURNS: JSON with the horoscope text, date, and period. NEXT: Use calculate_birth_chart first if you only need the raw chart data.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudeuser_nametimezone_offset

get_weekly_horoscope

Generate an in-depth, chart-aware weekly horoscope — AI-powered, not a generic template. WHEN TO USE: When an agent's user wants detailed weekly guidance that accounts for their specific birth chart and this week's exact transits. Unlike one-line rashifal predictions, this tool produces a nuanced, multi-paragraph reading that knows the user's ascendant, Moon nakshatra, current dasha, and how this week's transits aspect their natal placements. WHAT IT DOES: Computes the birth chart, detects this week's transit events, and generates a personalized weekly guidance message that accounts for planetary motion between week start and week end. RETURNS: JSON with horoscope text, iso_week, week_start, week_end, transit_events, and generated_at timestamp. NEXT: Use get_weekly_transit_events for just the deterministic events.

Parametersdayrequiredhourrequiredyearrequiredmonthrequiredminutelatitudelongitudeuser_nametimezone_offset

ask_cosmic_advisor

Ask an in-depth, chart-aware astrological question — AI-powered, not template-based. WHEN TO USE: When an agent's user asks an open-ended question about their life, chart, or future that needs deep Vedic interpretation. This is not a simple lookup table or template prediction — it reads the full natal chart, applies classical Jyotish principles (yogas, dashas, transits, dignity, house lords), and delivers a nuanced, multi-paragraph answer grounded in the specific planetary combinations present in that chart. WHAT IT DOES: Computes the full birth chart, builds structured chart context including planetary positions, house placements, nakshatras, and yogas, then generates an in-depth interpretation routed to the appropriate domain (career, relationships, health, finance, education, travel, property, general). RETURNS: JSON with the answer text, domain used, and the question. USAGE POLICY: Pro tier is for direct agent-to-user use only. Resale, white-labeling, or re-serving Cosmic Advisor answers to third parties requires an Enterprise license. Answers include VedaVisor attribution. NEXT: Use calculate_birth_chart if you only need raw data. Use ask_prashna for yes/no horary questions.

Parametersdayrequiredhourrequiredyearrequiredmonthrequireddomainminutelatitudequestionrequiredlongitudetimezone_offset

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Visor integrations