
Wraps WorldTimeAPI to give Claude access to timezone data without requiring authentication. Exposes a single tool, list_timezones, which returns all available IANA timezone strings. Part of the larger Pipeworx gateway ecosystem that connects to 250+ data sources. You can use it standalone for basic timezone queries or through the ask_pipeworx natural language interface that routes questions to the appropriate tool automatically. Useful when you need Claude to work with time conversions, scheduling across regions, or validating timezone identifiers. Works over streamable HTTP, so no local installation required.
Timezone MCP — wraps timeapi.io (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_time_by_timezone | Get the current date and time in a specific IANA timezone (e.g. "America/New_York", "Europe/London", "Asia/Tokyo"). |
list_timezones | List all 590+ IANA timezone strings available from timeapi.io. |
get_time_by_ip | Get the current date and time for the timezone of an IP address (resolved via ip-api.com → timeapi.io). |
convert_time | Convert a datetime from one timezone to another. If no time is provided the current time in the source timezone is used. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"timezone": {
"url": "https://gateway.pipeworx.io/timezone/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/timezone/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 Timezone data" })
The gateway picks the right tool and fills the arguments automatically.
MIT