Scheduler MCP. Calculate deadlines across continents, ignoring holidays and timezones.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Business Timezone & Holiday Scheduler lets your AI calculate accurate deadlines, skipping weekends and all global public holidays. It also converts exact meeting times between complex timezones (like America/Sao_Paulo to Asia/Tokyo) with zero guesswork.
What your AI agents can do
Add business days
Calculates a future date by adding specific working days while automatically ignoring weekends and public holidays for the chosen country.
Convert timezone
Converts an exact date and time between two global zones using their IANA timezone identifiers (e.g., America/New_York).
Determine a final date by adding a set number of business days while automatically skipping weekends and national holidays for a specified country.
Change an exact date and time from one complex global timezone to another, accounting for real-world offset rules (like DST).
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Business Timezone & Holiday Scheduler: 2 Tools
Use these two tools to manage complex scheduling logic, calculate working days based on country holidays, and accurately convert times across any globe timezone.
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 Vinkius019e3872add business days
Calculates a future date by adding specific working days while automatically ignoring weekends and public holidays for the chosen country.
019e3872convert timezone
Converts an exact date and time between two global zones using their IANA timezone identifiers (e.g., America/New_York).
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 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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 server provides 2 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Calendar math shouldn't require a PhD in global logistics.
Right now, setting up complex timelines is a manual nightmare. You open your CRM for the start date, then you have to jump over to Google Calendar to check if that end date lands on a weekend. If it does, you figure out which country's holidays apply and cross-reference that in a spreadsheet. It’s slow, and human error is built into every single click.
With this MCP, the agent handles all of that background work. You simply tell your agent, 'The deadline is 45 business days after X.' The system figures out weekends, checks the national holiday list for that country, skips them all, and spits out one perfect date. It's instant.
Convert Timezones with Business Timezone & Holiday Scheduler MCP
Before this, if you needed to schedule a meeting from New York to Sydney, you had to do the calculation manually in multiple time zone converters. You'd have to confirm if Daylight Saving Time was active and if the dates crossed midnight or even another day entirely.
Now, inputting two zones is enough. The agent calculates the exact moment they overlap, regardless of DST shifts or how many hours separate them. It just works.
What you can do with this MCP connector
LLMs struggle with calendars. They forget that daylight saving rules change yearly or that a national holiday exists on a specific date. This MCP fixes those scheduling errors by giving your agent real-time calendar and geographic intelligence. You can ask for a deadline 45 business days out, and the system automatically calculates it while skipping weekends and any known public holidays for that country.
Need to schedule a call between London and Sydney? It handles the precise timezone shift flawlessly.
If you're building an agent that needs to coordinate deadlines across multiple platforms—say, calculating a project launch date using this MCP, then passing that final time into a messaging service or a billing system—you can chain those operations together. This integration capability is managed by Vinkius; it runs every call inside its own secure sandbox, ensuring your keys are used only in transit and never stored on disk.
You connect once to the Vinkius platform from any compatible client, giving your agent access to this global scheduling power without compromising security.
019e3872-39e6-70e6-8556-3e3cfa80eb7b 
How Scheduler MCP Works
- 1 First, specify the start date and any necessary constraints, such as a country code or target IANA time zone.
- 2 Next, tell your agent what calculation to perform—for example, 'find the date 90 days from now' or 'convert this meeting time'.
- 3 The MCP returns the precise, corrected final date or time, adjusted for holidays and global timezone offsets.
The bottom line is your agent gets dates that match reality, not just what a model predicts.
Who Is Scheduler MCP For?
Project managers who spend hours cross-referencing Google Calendar and national holiday sites. Global sales teams coordinating pitches across continents. Operations analysts needing accurate SLA tracking for international contracts.
Needs to calculate a final milestone date 60 business days out, making sure the deadline won't fall on a national holiday in any of the target countries.
Constantly converting meeting times between headquarters (e.g., New York) and client sites (e.g., São Paulo), needing to know the exact local time for every call.
Tracking contract end dates where the Service Level Agreement (SLA) is measured in business days, requiring accurate holiday skipping logic by country code.
What Changes When You Connect
- Stop worrying about date drift. Use
add_business_daysto calculate true working deadlines by automatically skipping weekends and national public holidays for any country code you specify. - Eliminate scheduling confusion. The
convert_timezonetool handles the complex math of IANA timezones, so a meeting booked in Tokyo shows up correctly in London’s calendar. - Build full automations using Vinkius. You can chain this MCP with other services—like sending a reminder message after calculating an SLA deadline—all through one AI agent.
- Accuracy is key. The system handles real-world time shifts, including daylight saving time changes, which basic date arithmetic always misses.
- Save effort on complex scheduling logic. By separating the business day calculation from the timezone conversion, your agent remains reliable even in multi-step workflows.
Real-World Use Cases
Finalizing an international contract deadline
A compliance officer needs to know when a 90-day service agreement expires. They ask the agent, which uses add_business_days with country code 'BR', and get back a precise date that accounts for Brazilian holidays.
Organizing a global kickoff meeting
The PM needs to find the best time slot for five people across three continents. They use convert_timezone repeatedly until the agent proposes a window that works equally well for everyone's local working hours.
Calculating project completion timeline
A development team needs an estimate of when their product will launch, measured in business days from today. The agent uses add_business_days to factor in upcoming national holidays and weekend shutdowns for the US market.
Scheduling a follow-up call after conversion
The sales director converts a client's time zone first using convert_timezone, then immediately uses that converted date as input to calculate the next available business day using add_business_days.
The Tradeoffs
Using simple calendar math
Calculating a deadline by just adding 45 days, which results in a date that falls on a Saturday or a major public holiday.
→
Always use the add_business_days tool and specify the country code. This ensures the agent jumps over weekends and national holidays for accuracy.
Ignoring timezones completely
Simply converting a date string without specifying which timezone it came from, leading to off-by-one day errors.
→
Always use convert_timezone and provide the full IANA zone strings for both the source and destination times.
Mixing up calculations
Running a timezone conversion, then trying to add business days using the converted time as input without re-validating its local date context.
→
If you convert zones first, use the resulting accurate date/time output immediately as the starting point for add_business_days.
When It Fits, When It Doesn't
Use this MCP if your workflow involves any scheduling across time zones or relies on business day counts. For instance, if an SLA is measured in 'working days' or if you must coordinate meetings between regions like Europe and Asia, this tool is necessary. Don't use it if you only need to count calendar days (e.g., 30 days from now) because basic date arithmetic works fine for that. If your sole goal is general text generation or data formatting, then stick with a standard LLM function; don't bother connecting this MCP.
Common Questions About Scheduler MCP
How does add_business_days handle multiple countries? +
You specify a single country code (e.g., 'US' or 'JP') when calling add_business_days. The tool uses that code to query the public Nager.Date API and skip all known national holidays for that specific region.
Is convert_timezone reliable across DST changes? +
Yes, it is built on IANA time zone strings. This means it accounts for every historical rule change, including when a timezone shifts clocks forward or back due to Daylight Saving Time.
Can add_business_days calculate dates in the UK? +
Yes. You just need to provide 'GB' as the country code for add_business_days. The tool will then skip all weekends and any recognized national holidays in Great Britain.
What timezone format does convert_timezone require? +
It requires standardized IANA zone strings, like 'America/New_York' or 'Asia/Tokyo'. These are the official identifiers that describe a region’s time rules.
Can I use `convert_timezone` immediately after calculating a date using `add_business_days`? +
Yes, you can pass the output of one tool directly into another. This lets your agent calculate a deadline with add_business_days, and then convert that resulting specific date and time for international teams in a single workflow.
What happens if I provide an unsupported timezone string to `convert_timezone`? +
The MCP will return a structured error code indicating the invalid or unsupported IANA zone. Your agent can automatically catch this specific failure and prompt you for the correct timezone, preventing workflow interruption.
Does `add_business_days` require the starting date to be a weekday? +
No, it accepts any calendar date, including weekends or holidays. It simply uses that initial day as the reference point and begins counting forward, skipping non-business days until the final target is reached.
Are there rate limits when I run multiple calls to `add_business_days` in a sequence? +
For typical use cases, no explicit hard limit exists. Vinkius manages infrastructure capacity, allowing high throughput for sequential tool calls within your established budget.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.