MCP server for China public holidays and lunar calendar: solar-lunar conversion and yearly schedule.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
列出指定年份的全部中国法定节假日安排，包括放假日期和调休上班日期。支持2025、2026年
年份，如 2026
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http calendar-mcp https://pianam.cn/calendar-mcp/mcp
列出指定年份的全部中国法定节假日安排，包括放假日期和调休上班日期。支持2025、2026年
| Argument | Type | Description |
|---|---|---|
| year* | integer |
| 年份，如 2026 |
{
"type": "object",
"required": [
"year"
],
"properties": {
"year": {
"type": "integer",
"description": "年份，如 2026"
}
},
"additionalProperties": false
}查询指定公历日期的中国法定节假日或调休安排，同时返回农历信息。支持2025、2026年。参数date格式：YYYY-MM-DD
| Argument | Type | Description |
|---|---|---|
| date* | string | 公历日期，格式 YYYY-MM-DD，如 "2026-10-01" |
{
"type": "object",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"description": "公历日期，格式 YYYY-MM-DD，如 \"2026-10-01\""
}
},
"additionalProperties": false
}将公历日期转换为农历日期，返回农历年月日、是否闰月、生肖、干支等信息
| Argument | Type | Description |
|---|---|---|
| day* | integer | 公历日，如 17 |
| year* | integer | 公历年，如 2026 |
| month* | integer | 公历月，如 2 |
{
"type": "object",
"required": [
"year",
"month",
"day"
],
"properties": {
"day": {
"type": "integer",
"description": "公历日，如 17"
},
"year": {
"type": "integer",
"description": "公历年，如 2026"
},
"month": {
"type": "integer",
"description": "公历月，如 2"
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 9, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.