# Business Timezone & Holiday Scheduler MCP > Business Timezone & Holiday Scheduler calculates exact business days that skip weekends and national public holidays globally. It converts dates and times flawlessly between complex timezones (like America/New_York to Asia/Tokyo), handling DST shifts and leap years automatically. Stop relying on generic calendars; use this MCP for precise, global scheduling. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** timezone-conversion, public-holidays, scheduling, global-business, date-calculation, executive-assistant ## Description Managing deadlines across different regions is a nightmare if you don't have reliable date intelligence. You can ask your agent for a deadline 60 days from now, specifying the country code—say, Brazil or Japan—and it automatically handles skipping every weekend and all local public holidays. This eliminates the common error of scheduling something on a bank holiday. Need to coordinate a meeting between London, Singapore, and São Paulo? Just tell your agent the start date and the timezones; it spits out the accurate converted time for everyone involved, accounting for complex offsets. Because this MCP is hosted in the Vinkius catalog, you can connect it once from any compatible client and use reliable scheduling intelligence alongside thousands of other services. ## Tools ### add_business_days Adds a specific number of working days to a starting date, skipping weekends and optional national public holidays based on the country code provided. ### convert_timezone Converts an exact date and time from one specified timezone string to another using IANA standards. ## Prompt Examples **Prompt:** ``` If I sign a contract in Brazil today (2026-05-15), what is the exact date 45 business days from now, skipping Brazilian holidays? ``` **Response:** ``` I calculated 45 business days from 2026-05-15. Skipping all weekends and public holidays in Brazil (BR), your deadline falls precisely on: **July 20, 2026**. ``` **Prompt:** ``` Convert our project launch time (October 15, 2026 at 14:30 in New York) to Tokyo time. ``` **Response:** ``` I converted the timezone. **From (America/New_York):** October 15, 2026 at 2:30 PM **To (Asia/Tokyo):** October 16, 2026 at 3:30 AM Your launch in Tokyo will be early the next morning. ``` ## Capabilities ### Calculate business deadlines Asks for a future date by adding specific days while ignoring weekends and national holidays in a country you name. ### Convert meeting times globally Converts an exact date and time between any two complex IANA timezones, accounting for real-world offset rules. ## Use Cases ### Setting a global contract deadline A law firm needs to set a 60-day client response window starting today in India. They use `add_business_days` with the country code 'IN' to guarantee the final date skips all local bank holidays and weekends. ### Scheduling an international board call The CEO needs a meeting time that works for teams in New York, Tokyo, and London. They use `convert_timezone` with specific IANA strings to find the single overlapping 30-minute window. ### Calculating project ramp-up time An engineering team needs to know when a feature will be complete, based on adding 45 working days starting next month in Canada. They run `add_business_days` with 'CA' to get the accurate final date. ### Handling time zone changes A streaming service needs to confirm a global content launch time from LA to Berlin. Using `convert_timezone` ensures the agent correctly accounts for Daylight Saving Time differences across those two zones. ## Benefits - Never miss a deadline because of a local holiday. Use `add_business_days` to calculate project milestones while automatically skipping national public holidays in the country you specify. - Stop guessing meeting times. With `convert_timezone`, your agent handles complex IANA zones, giving you precise time matches between any two global locations. - Saves hours of manual checking. The MCP eliminates having to cross-reference multiple international holiday calendars and DST rules manually. - Builds reliable automation. You can embed perfect date math into custom workflows that previously required brittle internal code. - Confidence in scheduling. It ensures your deadlines are not just 'close enough,' but mathematically guaranteed working days, period. ## How It Works The bottom line is you get calendar math that actually respects global labor laws. 1. You tell your agent the starting date, the number of business days you need to add, and the country code (e.g., 'US' or 'FR'). 2. The MCP runs checks against public holiday APIs, skipping all weekends and any national holidays for that specific location. 3. Your agent receives a single, precise final date that is guaranteed to be a working day in the target country. ## Frequently Asked Questions **How does add_business_days handle Daylight Saving Time?** It automatically accounts for DST rules. You provide the starting date, and it calculates the future date respecting any seasonal offset changes in that country's calendar. **What IANA strings should I use with convert_timezone?** You must use the standard IANA time zone names (e.g., 'America/Los_Angeles' or 'Asia/Singapore'). These are precise enough for accurate conversion. **Can add_business_days skip holidays from multiple countries?** No, it requires a single country code (e.g., 'BR') to accurately query and skip that specific nation's public holidays. **Is convert_timezone better than just Google Calendar? ** Yes, because your agent can call this MCP directly. It routes the time data into a workflow instantly, rather than making you copy/paste it into an external calendar app. **If I use the add_business_days tool with an incorrect or impossible start date, how does it handle the error?** The MCP returns a structured JSON error message. This message pinpoints exactly which input parameter failed and why. You'll get clear details like 'Invalid Date Format' or 'Country Code Not Supported', letting you fix your prompt immediately. **Does the add_business_days tool automatically account for leap years when calculating dates?** Yes, it does. The underlying Nager.Date API handles calendar irregularities like leap days (February 29th) without you needing to specify them. You just input your start date and number of business days. **When using convert_timezone, what format should I use for the source date and time?** You must provide a full timestamp in ISO 8601 format along with the originating IANA timezone. This ensures the agent knows the exact context of the time before making any conversion. **Are there rate limits when running many calls to convert_timezone?** While Vinkius manages usage, the underlying API generally supports high throughput. For extremely large batch jobs, check the official Nager.Date documentation for specific rate guidelines. **Does this require an API key?** No. The timezone logic runs directly inside the Vinkius Edge process. For holiday lookups, it uses the free, public Nager.Date API without requiring authentication. **Why use this instead of letting the AI guess?** AIs do not have access to live calendars or global holiday databases. They will frequently schedule your deadlines on a Sunday or a major national holiday. This MCP enforces absolute temporal accuracy.