io.github.mohammad-abbasi-sh/feiertage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Unofficial read-only MCP server for German public holidays (gesetzliche Feiertage) — the feiertage-api.de API (bundesAPI project): holidays per year and federal state (Bundesland), is-it-a-holiday checks, the next holiday from a date, and holidays in a date range. No key, no login. State codes are the 2-letter codes (BW, BY, BE, BB, HB, HH, HE, MV, NI, NW, RP, SL, SN, ST, SH, TH) or NATIONAL for the nationwide holidays (Neujahrstag, Karfreitag, Ostermontag, Tag der Arbeit, Christi Himmelfahrt, Pfingstmontag, Tag der Deutschen Einheit, 1./2. Weihnachtstag). Holiday names are German; each dated holiday also carries its weekday (English + German). A few entries have no date (note_only: true) — they are notes, e.g. school-free days, not statutory holidays. Built by Mohammad Abbasi (mohammad-abbasi-sh) — https://almanibama.ir · https://mabbasi.ir — Germany MCP factory.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| feiertage_list_holidaysA | List the public holidays of one year in one German federal state. year: e.g. 2026 (default: current year). state: 2-letter code (BW, BY, BE, BB, HB, HH, HE, MV, NI, NW, RP, SL, SN, ST, SH, TH) or NATIONAL for the nationwide holidays (default NATIONAL). month: 1..12 to filter to one month (default: whole year). Entries with date null (note_only) are notes, not statutory holidays. |
| feiertage_is_holidayA | Is a date a public holiday in one German federal state? day: YYYY-MM-DD, e.g. 2026-12-25. state: 2-letter code or NATIONAL (default NATIONAL). Returns is_holiday plus the holiday name(s). |
| feiertage_next_holidayA | The next public holiday on or after a date in one German state. from_date: YYYY-MM-DD (default: today). state: 2-letter code or NATIONAL (default NATIONAL). Looks into the next year if the current year has no holiday left. |
| feiertage_holidays_betweenA | Public holidays in a date range in one German federal state. start_date / end_date: YYYY-MM-DD (max range ~2 years). state: 2-letter code or NATIONAL (default NATIONAL). |
| feiertage_list_statesA | All 16 German federal states (Bundesländer) plus NATIONAL (nationwide holidays) — the state codes the other tools accept. |
| feiertage_healthA | Check whether the feiertage-api.de API is reachable right now. Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings. |
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 6 tools
Each tool has a clearly distinct query shape: year/month listing, single-date check, next-holiday lookup, date-range scan, state code reference, and health probe. The only mild overlap is between feiertage_list_holidays with a month filter and feiertage_holidays_between, which can return similar data, but the descriptions make the intended use of each clear.
All six tools use the same feiertage_ prefix followed by a consistent verb_noun snake_case pattern (list_holidays, is_holiday, next_holiday, holidays_between, list_states, health). The convention is predictable and readable throughout.
Six tools is a well-scoped set for a read-only holiday lookup service; every tool maps to a distinct query need (listing, checking, upcoming, range, state codes, availability). No filler or redundant endpoints.
The surface covers the full read-only lifecycle: discovering valid state codes, listing holidays, checking a date, finding the next one, scanning ranges, and probing API health. Minor gap: no tool to resolve a holiday name back to dates or to return holiday metadata beyond name/date, but agents can work around this via the listing tools.