# Timezone Offset Engine MCP for AI Agents AI Agent Connect

> Timezone Offset Engine MCP. It calculates precise time differences between two timezones for any date and time, including correct Daylight Saving Time (DST) handling. Stop letting your AI guess the time difference between cities; this tool uses the IANA database to provide accurate offsets every time.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_2nGb8lvudhQxRsFhULhhj2K1RpyPgzgWXA3NnLoE/ai-agent-connect
- **Tags:** timezone, dst, datetime, scheduling, iana-database, global-time

## Description

Timezone Offset Engine lets you get the exact time difference between two locations for any specific date and time. When you're building a scheduling agent, getting the time right is everything. If a user wants to book a meeting between London and São Paulo in July, a standard AI might get the Daylight Saving Time (DST) rules wrong. This Connector fixes that by using the Luxon library and the full IANA timezone database. It handles the heavy lifting of checking when clocks shift in different regions. You'll get the local times for both the source and target zones plus the exact offset in hours and minutes. It's a reliable way to keep your global operations on track, and it's one of the tools you'll find in the Vinkius catalog to ensure your agent never misses a beat on international coordination. Instead of forcing your agent to guess based on training data, you're giving it a direct line to the source of truth. This means no more missed calls or confusing shipping windows because of a one-hour shift that happened overnight. It's about providing your users with a tool that actually works the way they expect it to.

## Tools

### get_timezone_offset
Input two IANA zones and a date to get the exact hour and minute offset between them. This ensures your agent never hallucinates a time difference.

## Prompt Examples

**Prompt:** 
```
What's the time difference between London and São Paulo on July 15, 2025?
```

**Response:** 
```
**London (BST):** 08:00 | **São Paulo:** 04:00

*Offset: +4 hours (London is in DST, São Paulo is not).* 
```

**Prompt:** 
```
If it's 9am in Tokyo right now, what time is it in New York?
```

**Response:** 
```
**Tokyo:** 09:00 JST | **New York:** 20:00 EDT

*Offset: -13 hours.*
```

**Prompt:** 
```
Will the time difference between Berlin and Sydney change in March 2025?
```

**Response:** 
```
**Yes.** The offset changes because both regions have DST transitions.

*   **March 1:** Offset A
*   **March 31:** Offset B
```

## Capabilities

### Get precise offsets
Get the exact hour and minute difference between two cities for any specific date.

### Handle DST automatically
The engine knows exactly when clocks shift in every region.

### Support 400+ timezones
Access the full IANA database for global coverage.

### Show local times
See the actual clock time for both source and target zones.

### Provide bidirectional data
Get the offset in both directions for easier comparison.

## Use Cases

### Booking a meeting between London and São Paulo
An agent uses get_timezone_offset to see if London's DST is active on a specific July date to suggest the best meeting time.

### Calculating shipping windows for Tokyo to New York
The agent checks the exact offset for a specific delivery day to provide accurate arrival estimates for customers.

### Syncing global team calendars
A user asks for the time difference between Berlin and Sydney in March, and the agent confirms the DST shift.

### Automating flight alerts
The system checks local times for multiple hubs to ensure alerts hit at the right hour for the user.

## Benefits

- Eliminate DST hallucinations by using the IANA database through get_timezone_offset.
- Ensure meeting accuracy for global teams by getting real-time local clock data.
- Simplify international shipping logs with precise hour and minute offset calculations.
- Reduce manual lookups by letting your agent handle 400+ global timezones automatically.
- Build more reliable travel itineraries by checking specific date offsets for any city.

## How It Works

The bottom line is your agent gets perfect time math for global scheduling.

1. Provide two IANA timezone names and an optional date.
2. The engine queries the Luxon database to check DST rules.
3. You get the exact hour and minute offset and the local time for both zones.

## Frequently Asked Questions

**Does the Timezone Offset Engine handle Daylight Saving Time?**
Yes, it uses the full IANA database to ensure that DST shifts are accounted for correctly based on the specific date you provide.

**Can I use Timezone Offset Engine for any city in the world?**
It supports over 400 IANA timezones, covering almost every major city and region globally.

**How does the Timezone Offset Engine work for specific dates?**
You provide two timezone names and a date, and the Connector returns the exact hour and minute difference for that specific moment.

**Is the Timezone Offset Engine good for scheduling meetings?**
It's perfect for that because it gives you the local time for both locations, making it easy to see the best time to connect.

**Can I use Timezone Offset Engine to find out if a city is currently in DST?**
Yes, the tool explicitly tells you whether each zone is currently in Daylight Saving Time when it returns the offset.

**Does it handle Daylight Saving Time?**
Yes. This is the primary reason this tool exists. It calculates offsets at the exact moment you specify, correctly accounting for all DST transitions worldwide.

**What datetime format should I use?**
ISO 8601 format: YYYY-MM-DDTHH:mm:ss (e.g. '2025-07-15T14:00:00'). If omitted, the engine uses the current moment.

**How many timezones are supported?**
All 400+ IANA timezone identifiers, including regional variants like America/Argentina/Buenos_Aires and special zones like UTC and GMT.