Time Zone Converter and Meeting Overlap Finder

Convert a date and time into many time zones with correct daylight-saving handling, or find the windows when everyone is inside working hours. No web calls, no AI: it uses the IANA time zone database built into the Node.js runtime. Callable by developers and by AI agents through Apify's MCP server (https://mcp.apify.com).

• convert: for each target zone, the local time with offset, abbreviation, weekday, DST flag and the day shift versus the source (so "tomorrow" is never missed). Accepts a local time in a source zone (2026-11-03T15:00 + Asia/Dubai) or an exact instant (2026-11-03T11:00:00Z).
• overlap: for a calendar day (read in the first zone of your list), the 30-minute-granular windows where every zone is within working hours, with local start and end per zone. Handles half-hour and 45-minute zones (India, Nepal) and DST differences between regions.

Input

Field	Meaning
mode	convert (default) or overlap
dateTime, fromTimeZone	convert: the moment and its zone
timeZones	IANA names such as Asia/Dubai, up to 50
date, workdayStart, workdayEnd, minMeetingMinutes, weekdaysOnly	overlap options

Output example

Real output for 2026-11-03T15:00 in Asia/Dubai converted to America/New_York:

{
  "kind": "conversion", "input": "2026-11-03T15:00", "source_time_zone": "Asia/Dubai",
  "utc": "2026-11-03T11:00:00.000Z", "time_zone": "America/New_York",
  "local_time": "2026-11-03T06:00:00-05:00", "utc_offset": "-05:00", "abbreviation": "EST",
  "weekday": "Tuesday", "is_dst": false, "day_shift_vs_source": 0,
  "ambiguous_source_time": false, "warning": null, "error": null
}

Overlap for Dubai and London on Mon 12 Jan 2026, 09:00-17:00 each: one window, 09:00-13:00 UTC, which is 13:00-17:00 in Dubai and 09:00-13:00 in London.

Important limits (read before relying on it)

• Daylight-saving edge cases are reported, not hidden. A local time that does not exist (a spring-forward gap, such as 02:30 on 8 Mar 2026 in New York) returns an error. A local time that occurs twice (fall-back) uses the earlier instant and sets ambiguous_source_time with a warning.
• Accuracy depends on the time zone data in the runtime (Node.js with ICU / IANA tz data, https://www.iana.org/time-zones). Governments change rules at short notice; very recent or future rule changes may be missing until the runtime updates. Dates far in the future follow the current rules.
• Overlap uses Monday to Friday everywhere when weekdaysOnly is on. It does not know regional weekends (for example Friday-Saturday), public holidays, lunch breaks or individual calendars. One working-hours range applies to all zones.
• Overlap works in 30-minute steps on one calendar day of the first zone, so a window that crosses midnight of that zone is cut at the day boundary.
• abbreviation is whatever the runtime prints in US English; many zones show forms like GMT+4 rather than a named abbreviation.

Pricing (pay-per-event)

Uses Apify's built-in apify-default-dataset-item event: each zone conversion, or each overlap report, is one result. The owner sets the price in Apify Console. Suggested: USD 2.00 per 1,000 results. No priced direct competitor was found; the nearest are an MCP time server and a thin wrapper (see apify/RESEARCH-3.md).

FAQ

Does it call a website? No.

Can I convert many moments at once? One moment per run in this version; a run can fan out to up to 50 zones.

Does it support Windows time zone names? No, IANA names only.