
Wraps the Nager.Date API to give Claude access to public holiday data across countries without requiring authentication. This is the kind of server you'd reach for when building scheduling tools, calendar features, or any application that needs to be aware of regional holidays. Pipeworx hosts it as part of their larger gateway offering (673+ data sources), but you can connect to just the holidays endpoint if that's all you need. The implementation uses streamable HTTP transport and offers a plain English query interface through ask_pipeworx alongside direct tool calls. Free to use, MIT licensed.
Holidays MCP — wraps Nager.Date API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_holidays | Get all public holidays for a country and year. Returns holiday names and dates. Provide country code (e.g., "US", "GB", "DE") and year. |
is_today_holiday | Check if today is a public holiday in a given country. Returns whether it's a holiday and the holiday name if applicable. Provide country code (e.g., "US", "GB"). |
next_holidays | Get upcoming public holidays from today onward for a country. Returns holiday names and dates. Provide country code (e.g., "US", "GB", "DE"). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"holidays": {
"url": "https://gateway.pipeworx.io/holidays/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/holidays/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Holidays data" })
The gateway picks the right tool and fills the arguments automatically.
MIT