Kundlit Vedic Astrology MCP Server (com.kundlit/astro)

Kundlit Vedic Astrology is an MCP server that provides free Vedic astrology computations for AI assistants via the Model Context Protocol. It exposes 17 tools (discovered dynamically) and supports daily panchang and muhurta timings, city-based calculations, birth charts, matching, dosha checks, and calendaring.

🛠️ Key Features

Daily panchang and muhurta timings for any city
Janam kundali birth charts
Kundli milan (ashtakoot) matching
Dosha checks and dasha periods
Transits, festival and eclipse calendars
Vedic numerology
17 MCP tools (dynamically discovered)

🚀 Use Cases

Generate daily Panchang and Muhurta data for a location
Compute birth charts (janam kundali) for individuals
Run kundli matching (ashtakoot) and dosha evaluations
Retrieve transit and eclipse/festival calendar information

⚡ Developer Benefits

Tooling for panchang/muhurta, kundali, matching, and numerology through MCP
Tool discovery supports integration with 17 available capabilities
Includes prompts and documentation resources

⚠️ Limitations

Scope is limited to the Vedic astrology topics listed (e.g., panchang, kundali, doshas, transits, numerology).

Kundlit Vedic Astrology — MCP Server

Kundlit MCP server on Glama

Free Vedic astrology computation for AI assistants over the Model Context Protocol: daily panchang and muhurta timings for any city, janam kundali birth charts, kundli milan (ashtakoot) matching, dosha checks, dasha periods, transits, festival and eclipse calendars, and Vedic numerology — 17 tools (discovered dynamically), plus prompts and documentation resources.

Results are deterministic — computed live with the Swiss Ephemeris on the sidereal zodiac (Lahiri ayanamsa) — and backed by classical-text citations on kundlit.com.

Server URL: https://kundlit.com/api/mcp (hosted, Streamable HTTP)
Auth: none — no account, no API key
Rate limit: 30 requests/minute/IP
Docs: https://kundlit.com/mcp
Privacy: https://kundlit.com/privacy · Support: support@kundlit.com

Install

1. `npx` (works with every client, including stdio-only ones)

bash

npx -y @kundlit/mcp

That starts a local stdio MCP server which proxies to the hosted endpoint. Point any client at it by command:

Claude Desktop — claude_desktop_config.json:

json

{
  "mcpServers": {
    "kundlit-astro": {
      "command": "npx",
      "args": ["-y", "@kundlit/mcp"]
    }
  }
}

Cursor — .cursor/mcp.json, or any client that reads a generic .mcp.json:

json

{
  "mcpServers": {
    "kundlit-astro": {
      "command": "npx",
      "args": ["-y", "@kundlit/mcp"]
    }
  }
}

Installed globally (npm i -g @kundlit/mcp) the binary is kundlit-mcp, so "command": "kundlit-mcp" with no args works too.

2. Direct Streamable HTTP (clients with remote-server support)

No bridge process needed — connect straight to the URL.

Claude Code:

bash

claude mcp add --transport http kundlit https://kundlit.com/api/mcp

Config file:

json

{
  "mcpServers": {
    "kundlit-astro": {
      "type": "http",
      "url": "https://kundlit.com/api/mcp"
    }
  }
}

Claude (web/desktop): Settings → Connectors → Add custom connector → https://kundlit.com/api/mcp

Full per-client instructions, example prompts and limitations: https://kundlit.com/mcp

What is in this repository

The npm package @kundlit/mcp published from here is a thin client: a bidirectional JSON-RPC pump between a local StdioServerTransport and a StreamableHTTPClientTransport aimed at https://kundlit.com/api/mcp. It contains no astrology logic and no copy of the tool list, so tools added or renamed on the hosted server are picked up with no package update.

Frames are forwarded unmodified in both directions with one deliberate exception: if the hop to the hosted server fails, the bridge answers the pending request locally with a JSON-RPC -32001 error (bin/cli.js) rather than letting the local client hang forever on a reply that is never coming. That error is synthesised by the bridge and was never sent by the server.

The astrology server itself is hosted at kundlit.com and its source is not public. The manifests here (.mcp.json, server.json, .claude-plugin/plugin.json) exist so MCP clients, registries and directories can discover and install it.

Bridge options

code

kundlit-mcp [--url <endpoint>]

  --url <endpoint>   Hosted MCP endpoint (default https://kundlit.com/api/mcp).
                     Also settable via KUNDLIT_MCP_URL; --url wins.
  -h, --help         Usage and a config snippet.
  -v, --version      Package version.

stdout carries JSON-RPC and nothing else; all diagnostics, including --help and --version output, go to stderr. Requires Node.js 18 or newer.

Docker

bash

docker build -t kundlit-mcp .
docker run -i --rm kundlit-mcp

The container speaks MCP over stdio, so run it with -i and no TTY.

Development

bash

npm install
node scripts/smoke.mjs   # end-to-end check against the live hosted server

Capabilities

17 tools, discovered dynamically via tools/list — panchang, muhurta and choghadiya windows, janam kundali, ashtakoot matching, manglik / kaal sarp / sade sati checks, dasha periods, transits, pancha pakshi, year events, eclipses, and numerology. Prompts and documentation resources (kundlit://docs/methodology, kundlit://docs/usage-guide) are likewise discovered at runtime; ask your client to list them rather than relying on a list in this README.

Example prompts

"What is today's panchang in Jaipur? When is rahu kaal?"
"Make a janam kundali for 14 March 1992, 6:45 am, Lucknow — which mahadasha am I running?"
"Find me a good time tomorrow in Pune to sign a lease — avoid rahu kaal and bhadra."
"All ekadashi dates in 2026 for Varanasi."

Notes

Free-text place (any city worldwide) is preferred; latitude/longitude/IANA timezone also accepted. Year tools snap to the nearest of 50 supported cities.
Results are informational and not a substitute for professional advice.
Every result carries a Source: attribution line — please keep it intact; that attribution is the price of free access.

License

MIT — see LICENSE.

date	string	optional	Gregorian date to compute, YYYY-MM-DD, e.g. 2026-07-25. Years 1200-2400. Omit to get today's date at the given place (not the server's date).
place	string	optional	Place as free text, "City, State, Country" -- e.g. "Jaipur, Rajasthan, India". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.
latitude	number	optional	Latitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.
longitude	number	optional	Longitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.
timezone	string	optional	IANA timezone name, e.g. "Asia/Kolkata" or "America/New_York" (never an offset like "+05:30"). Required when latitude/longitude are used; ignored when `place` is given.

birth_date	string	required	Birth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected).
birth_time	string	required	Birth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart.
place	string	optional	Place as free text, "City, State, Country" -- e.g. "Jaipur, Rajasthan, India". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.
latitude	number	optional	Latitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.
longitude	number	optional	Longitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.
timezone	string	optional	IANA timezone name, e.g. "Asia/Kolkata" or "America/New_York" (never an offset like "+05:30"). Required when latitude/longitude are used; ignored when `place` is given.

person_a	object	required	First person: gender plus birth date, birth time and place (or coordinates + timezone).
person_b	object	required	Second person: same fields as person_a. Their birth place may differ from person_a's.

birth_date	string	required	Birth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected).
birth_time	string	required	Birth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart.
place	string	optional	Place as free text, "City, State, Country" -- e.g. "Jaipur, Rajasthan, India". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.
latitude	number	optional	Latitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.
longitude	number	optional	Longitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.
timezone	string	optional	IANA timezone name, e.g. "Asia/Kolkata" or "America/New_York" (never an offset like "+05:30"). Required when latitude/longitude are used; ignored when `place` is given.

birth_date	string	required	Birth date in the Gregorian calendar as YYYY-MM-DD, e.g. 1992-03-14. Years 1200-2400 only, and it must be a real calendar date (2023-02-29 is rejected).
birth_time	string	required	Birth time on the local clock at the birth place, HH:MM in 24-hour format (00:00-23:59), e.g. 06:45 or 18:20. Not UTC. Required and not defaulted: the ascendant moves about one degree every four minutes, so a guessed time gives a guessed chart.
place	string	optional	Place as free text, "City, State, Country" -- e.g. "Jaipur, Rajasthan, India". Preferred input: it is geocoded to coordinates and an IANA timezone server-side, and any city worldwide works. Omit only if you pass latitude + longitude + timezone instead.
latitude	number	optional	Latitude in decimal degrees, -90 to 90, north positive (Delhi = 28.6139). Use only when `place` is omitted, and then longitude and timezone are required too.
longitude	number	optional	Longitude in decimal degrees, -180 to 180, east positive (Delhi = 77.2090). Use only when `place` is omitted.
timezone	string	optional	IANA timezone name, e.g. "Asia/Kolkata" or "America/New_York" (never an offset like "+05:30"). Required when latitude/longitude are used; ignored when `place` is given.
as_of_date	string	optional	Evaluate Saturn's position as of this date, YYYY-MM-DD, years 1200-2400. Omit for today. Use it to ask 'was I in sade sati in 2019' or 'will I be in 2031'.

Kundlit Vedic Astrology