Business Timezone & Holiday Scheduler MCP for AI. Calculate deadlines that respect global holidays.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
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.
What your AI can do
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.
Asks for a future date by adding specific days while ignoring weekends and national holidays in a country you name.
Converts an exact date and time between any two complex IANA timezones, accounting for real-world offset rules.
Ask an AI about this
Waiting for input…
Business Timezone & Holiday Scheduler: 2 Tools
This MCP gives you two specific tools to calculate complex business timelines, including adding working days or converting times across global time zones.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Business Timezone & Holiday Scheduler on VinkiusAdd Business Days
Adds a specific number of working days to a starting date, skipping weekends and optional national public holidays based on the country...
Convert Timezone
Converts an exact date and time from one specified timezone string to another using...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Business Timezone & Holiday Scheduler, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Nager.Date API. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Coordinating a meeting across three different continents is messy.
Today, setting up an international call means opening multiple time zone converter tabs. You copy the start date and time into one widget, then paste it into another for a second location, repeating that process until you get all three zones to agree on a single slot. It's tedious, error-prone, and takes forever.
With this MCP, you just tell your agent the initial time and list out every zone involved. The system calculates the overlap, showing you one clean answer for everyone. You get instant cross-continental time alignment.
Using `add_business_days` ensures deadlines are actually achievable.
Without this tool, if a project manager calculates 45 working days and hits a local holiday (like Labor Day in the US or Golden Week in Japan), they have to manually reset their timeline, delaying everything. That's wasted time.
Now you just run `add_business_days` with the country code. The MCP handles all those calendar checks for you; it skips every bank day and weekend, giving you a reliable completion date.
What your AI can actually do with this
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.
019e3872-39e6-70e6-8556-3e3cfa80eb7b Here's how it actually works
The bottom line is you get calendar math that actually respects global labor laws.
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').
The MCP runs checks against public holiday APIs, skipping all weekends and any national holidays for that specific location.
Your agent receives a single, precise final date that is guaranteed to be a working day in the target country.
Who is this actually for?
Global program managers, remote operations teams, and anyone who schedules meetings or project deadlines across multiple time zones. If your job involves coordinating with partners overseas, this MCP is for you.
Needs to set a 90-day project milestone that hits only on a working day in the client's home country.
Coordinates sales kickoff calls between HQ (New York) and EMEA offices, requiring accurate time conversion for multiple regions.
Calculates the official start date or completion date for international contractors that must skip local public holidays.
What Changes When You Connect
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.
See it in action
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.
The honest tradeoffs
Using simple calendar math
An agent calculates 30 days from now and suggests a date. The user assumes that because it's 30 days, it must be a working day.
Don't trust the count. Always use add_business_days and provide the country code to guarantee the final date is not a weekend or public holiday.
Manual time conversion
Comparing times in a spreadsheet, forgetting that one location observes DST while another doesn't. The resulting meeting invite sends people to different times.
Always use convert_timezone. Provide the full IANA zone names (like 'America/Chicago') for both endpoints; it handles all offset changes.
Ignoring country specifics
Asking for 30 business days without specifying a country. The agent might use generic rules that skip only weekends, missing major national holidays.
Specify the country code in add_business_days (e.g., 'JP'). This forces the MCP to query local public holiday lists.
When It Fits, When It Doesn't
Use this MCP if your core problem is date accuracy across jurisdictions or timezones. You need a single source of truth that handles DST shifts, leap years, and national holidays automatically. Don't use it if you just need to calculate simple days (e.g., 'add 10 days'). For basic arithmetic, standard tools are fine. But when your deadline must land on a specific working day in London or Shanghai—when the local rules matter—this is non-negotiable. If all your scheduling happens within one time zone and never crosses holidays, you might get by without it, but for global operations, this MCP is essential.
Questions you might have
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.
We've already built the connector for Business Timezone & Holiday Scheduler. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 2 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.