Skip to main content
Glama
socraticsurge

mcp-server-panchangam

Telugu Panchangam Calendar Feeds

Subscribable Telugu Panchangam feeds for 22 cities — delivered as .ics files you can add to Google Calendar, Apple Calendar, or Outlook.

Every day appears as an all-day event (no calendar blocking) with full Panchangam details in the description. Festival days — Ugadi, Vinayaka Chavithi, Deepavali, Maha Shivaratri, the Sankranti cluster, and 30+ more — are marked with 🪔 in the title; other special days (Ekadashi, Amavasya, Pournami, Pradosham, Sankranti, Eclipses) with ⚡.

Today's Panchangam at panchangam.astrochaganti.com

Subscribe

Visit the landing page to pick your city and calculation system and copy your webcal:// URL:

panchangam.astrochaganti.com

The site is also a daily toolkit: Today's Panchangam (any date, any city), Tarabalam · Muhurtam (good days and ranked time slots for up to four people by birth star, with Chandrabalam), and the Gochara chart with Rasi Phalalu (South Indian chart, transit verdicts and a computed daily reading). Guests can also create browser-local profiles from known astrology details. Local development and an explicitly activated public build can calculate Nakshatra, Padam, Janma Rashi, Lagna, and a reviewable D1 chart from date, exact time, and birthplace. Public builds fail closed until the licensed calculation service and place provider are approved; saved calculated profiles remain viewable. The name never leaves the browser. See the calculation and privacy contract. Drik Muhurtam searches also contain a source-backed candidate-time chart post-screen, guarded by an independent fail-closed flag. Public builds make no chart request unless VITE_ELECTION_CHART_API_ENABLED is exactly true; see the screening method and release boundary. Everything is shareable to WhatsApp.

Subscribe flow — pick a feed, copy the webcal URL, add to your calendar

Related MCP server: mcp-indian-astrology

What's in each day's event

  • Metadata — Samvatsara, Maasam, Paksham, Vaaram, solar and lunar signs

  • Pancha Anga — Tithi, Nakshatra, Yoga, Karana with start/end times

  • Sky markers — Sunrise, Sunset, Moonrise, Moonset

  • Auspicious windows — Brahma Muhurta, Abhijit Muhurta, Amrita Kalam

  • Inauspicious windows — Rahu Kalam, Gulika Kalam, Yamagandam, Varjyam, Durmuhurtham

  • Choghadiya — 8 day blocks with names

  • Eclipses — Solar and lunar eclipses with type (Total/Partial/Annular/Penumbral), visibility from your city, eclipse window, and Sutak period

  • Special Yogas — Sarvartha Siddhi, Amrita Siddhi, Visha, and Dagdha yogas based on weekday/tithi/nakshatra combination

Cities

Telugu Heartland — Hyderabad, Vijayawada, Visakhapatnam, Tirupati, Warangal, Guntur, Nizamabad, Rajahmundry, Kurnool, Nellore

Major Indian Metros — Bengaluru, Chennai, Mumbai, Delhi

International Diaspora — Dallas, San Jose, San Francisco, Edison (NJ), New York, London, Sydney, Dubai

Calculation Systems

System

Basis

Best for

Drik Ganita

Swiss Ephemeris (pyswisseph) — supports Lahiri, Raman, Krishnamurti, True Chitrapaksha ayanamsas

Modern apps, accurate sky events

Surya Siddhanta

Mean-motion algorithms from classical SS text

Traditions rooted in classical siddhantic calculation

Vakya

Surya Siddhanta + published correction tables

Traditional Telugu/Tamil printed Panchangams

MCP Server

mcp-server-panchangam is available on PyPI. It's a standard MCP stdio server (uvx mcp-server-panchangam), so it works with any MCP-compatible client or agent — Claude Desktop, Claude Code, Cursor, Windsurf, and custom agents built on the MCP SDK. Below are examples for a couple of common clients; for others, point your client's MCP config at the same uvx mcp-server-panchangam command.

Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "panchangam": {
      "command": "uvx",
      "args": ["mcp-server-panchangam"]
    }
  }
}

Claude Code — run once:

claude mcp add panchangam -- uvx mcp-server-panchangam

Available tools

Daily Panchangam

Tool

Description

get_panchangam

Full Panchangam for any date and city

get_muhurta

One day's auspicious/inauspicious windows (lighter call; use find_muhurta to search across days)

get_panchanga_shuddhi

Five-limb purity verdict (Sarva Shuddha → Sarva Ashuddha) with per-limb quality and reason

Planning across days

Tool

Description

get_panchangam_range

Compact Panchangam summary for each day in a range (max 31 days)

get_special_days

Named festivals, Ekadashi, Amavasya, Pournami, Pradosham, Sankranti, and Eclipses for a month

find_muhurta

Ranked auspicious time slots — activity-aware, every slot with its reasons

find_tarabalam_days

Tarabalam & Chandrabalam — days favourable for 1–4 people by birth star (and rashi)

Sky events

Tool

Description

get_combustion_calendar

Asta/Udaya (combustion entry/exit) periods for Mercury, Venus, Mars, Jupiter, Saturn

get_graha_yuddha

Graha Yuddha (planetary war) periods — winner, loser, timing in UTC

get_rashi_ingresses

All rashi sign-change events for the classical planets over a date range

get_eclipse_calendar

Solar and lunar eclipses with per-city visibility and Sutak timing

Gochara and personal transits

Tool

Description

get_graha_positions

All nine grahas at sunrise — rasi, nakshatra, retrograde, next-rasi dates

get_gochara

Gochara verdicts from a janma rashi — houses, vedha, Sade Sati / Ashtama Shani

get_rasi_phalalu

Deterministic daily reading rendered from computed facts

Intraday timing

Tool

Description

get_daily_horas

24 planetary hours (horas) for the day, starting at sunrise with the weekday lord

get_lagna_transitions

Ascendant (Lagna) sign boundaries tracking the eastern horizon across the day

Utility

Tool

Description

list_supported_cities

22 pre-configured cities with lat/lon/timezone

All tools accept any free-text city name. Pre-configured cities resolve instantly; any other city is geocoded via OpenStreetMap. You can also pass latitude, longitude, and timezone directly.

Drik-system tools that accept a city or date also accept ayanamsa=lahiri|raman|krishnamurti|true_chitrapaksha (default: lahiri). Full API documentation and parameter details: mcp-server-panchangam on PyPI.

How it works

Feeds are generated on the 1st of every month via GitHub Actions, covering 18 months ahead. They are served as static .ics files from GitHub Pages — zero hosting cost.

GitHub Actions (monthly cron)
  → python -m telugu_panchangam.generate   (22 cities × 3 systems = 66 feeds)
  → feeds/*.ics
  → GitHub Pages (webcal:// subscriptions)

Maintenance and roadmap

The active maintenance queue is the Telugu Calendar Utilities GitHub Project. Use the linked status and priority fields to see what is planned, in progress, or ready for review. File defects and feature proposals in repository Issues.

The CSV files and phase plans under docs/tracking/ are preserved historical records; they are not a second backlog.

Documentation

The repository is the canonical documentation source. Start with the documentation standard for where current reference, operations, decisions, and historical material belong, then use the computation reference index for the detailed system map. A searchable VitePress projection is built from these files at /docs/; it is disposable presentation output and does not replace the repository as the source of truth.

Development

python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
npm install
python tools/verify_project.py
python -m telugu_panchangam.generate   # writes to feeds/

Available Tools

1 tool
get_special_daysA

Returns a JSON list of special days in a given month: Ekadashi (fasting days), Amavasya (new moon), Pournami (full moon), Pradosham, Sankranti, and Eclipses. Args: year=e.g. 2026, month=1-12, city=city name (or pass latitude+longitude; timezone is derived if omitted), system=drik|surya_siddhanta|vakya (default: drik).

ParametersJSON Schema
NameRequiredDescriptionDefault
cityYes
yearYes
monthYes
systemNodrik
latitudeNo
timezoneNo
longitudeNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses key behaviors: the tool returns a JSON list, allows city name or coordinates, derives timezone if omitted, and defaults to the 'drik' system. It does not discuss authentication, rate limits, or error handling, but covers essential behavior for usage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the purpose and major argument details. It is front-loaded with the main function. Although somewhat lengthy, it avoids unnecessary words and is well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (signaled), the description focuses on inputs and behavior. It covers the required parameters and key optional ones, explaining fallbacks. The overall usage context is complete for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must compensate. It adds meaningful context for parameters: city can be name or lat/lon, timezone is derived automatically, system has default and possible values. It provides example values for year and month. While not all 7 parameters are fully detailed, the key ones are addressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns a JSON list of special days for a given month, explicitly listing types like Ekadashi, Amavasya, etc. This differentiates it from sibling tools that focus on other calendar events like eclipses or graha positions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context, specifying required arguments (year, month, city) and optional parameters with defaults. However, it does not explicitly state when to use this tool versus alternatives, though the list of special days implicitly guides selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

A3.9/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or overlap.

Naming Consistency5/5

With a single tool, the naming convention is inherently consistent.

Tool Count1/5

A panchangam server with only one tool is extremely limited; typical panchangam APIs offer many more elements like daily tithi, nakshatra, etc.

Completeness1/5

The tool only retrieves special days in a month, missing the vast majority of panchangam data (daily calendars, muhurta, etc.), making the server severely incomplete for its domain.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to access Indian Vedic astrology services including Panchang, Kundli, matchmaking, and festivals through natural language.
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Hosted Streamable HTTP MCP server for Vedic astrology: panchang, kundali (birth chart), matchmaking, dashas, doshas, muhurta and 16 tools computed by a precision astronomy engine.
    17
    53
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server providing Jyotish, Panchang, and Sanatan Dharma knowledge tools including panchang computation, festival calendars, muhurat windows, Jyotish concept explanations, and a source-grounded Sanatan encyclopedia with citations and provenance metadata.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/socraticsurge/telugu-calendar-utilities'

If you have feedback or need assistance with the MCP directory API, please join our Discord server