mcp-chrono
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| data-dir | No | Directory where holiday API responses are cached. Defaults to ~/.mcp-chrono/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_timeA | Get the current time in a specified timezone. Returns detailed time information including year, month, day, hour, minute, second, weekday, week of year, day of year, and UTC offset. |
| convert_calendarA | Convert between Gregorian (solar) and Chinese Lunar calendar. Includes Ganzhi (天干地支), zodiac animal, solar terms, and festival information. |
| convert_timezoneB | Convert a datetime from one timezone to another. Input can be an ISO 8601 string. |
| list_timezonesA | List IANA timezones with current offset and time. Uses the system's full IANA timezone database. Can filter by query text or continent. |
| calculate_timeB | Add or subtract time from a date. Supports Gregorian mode, Lunar mode, and anchor mode (calculate relative to a named festival). |
| date_diffA | Calculate the difference between two dates/times. Returns the difference in years, months, days, hours, minutes and also total days/hours/minutes. |
| parse_timestampB | Parse a Unix timestamp (seconds or milliseconds) or ISO 8601 string into detailed date/time components. |
| get_festivalsA | Get festivals, solar terms, and public holidays within a date range. Supports Chinese (lunar and solar) festivals and public holidays from various countries. |
| get_month_infoA | Get detailed information about a specific month including number of days, first/last day weekday, whether it's a leap year, and quarter. |
| countdownA | Calculate a countdown from now to a target date/time. Returns remaining days, hours, minutes, seconds and whether the date is in the past. |
| calculate_business_daysA | Calculate business days between two dates or add/subtract business days from a date. Skips weekends and optionally public holidays. |
| get_almanacA | Get Chinese almanac (黄历/老黄历) information for a specific date. Includes suitable activities (宜), things to avoid (忌), conflict zodiac (冲), lucky directions, and more. |
| manage_countdownB | Manage persistent countdown timers. Supports CRUD operations: set (create), get (read one), list (read all), delete. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose with no significant overlap. For example, calculate_business_days focuses on business days, calculate_time on time arithmetic, convert_calendar on calendar conversion, and get_almanac on almanac data. The descriptions specify unique functionalities, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as calculate_business_days, convert_timezone, get_festivals, and manage_countdown. This predictability aids in understanding and usage without any deviations in style.
With 13 tools, the count is well-scoped for a time and calendar utility server. Each tool serves a specific function, such as date calculations, conversions, and information retrieval, without redundancy or excessive bloat, fitting the domain appropriately.
The tool set provides comprehensive coverage for time and calendar operations, including calculations (e.g., date_diff, calculate_business_days), conversions (e.g., convert_calendar, convert_timezone), information retrieval (e.g., get_current_time, get_festivals), and management (e.g., manage_countdown). No obvious gaps are present for the stated purpose.