# Recurring Event Expander MCP for AI Agents MCP > The Recurring Event Expander takes complex calendar math and turns it into simple lists of dates. If you deal with recurring schedules—like 'the third Tuesday of every month'—this MCP calculates all the actual occurrence dates in a given timeframe, validates rules, and translates technical jargon into plain English summaries. ## Overview - **Category:** scheduling - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_yVWFO0rxR1OltATuNurj9QMd79zpTAItVWLQlFuA/mcp - **Tags:** rrule, rfc5545, calendar, scheduling, dates, automation ## Description Dealing with event recurrence rules (RFC 5545) can feel like decoding ancient calendar text. This MCP handles that complexity for your AI client. You don't have to worry about the intricate logic of intervals, specific weekdays, or exclusions. Instead, you just give it a technical rule string and ask questions. The system calculates every single date an event will occur within a defined window, giving you clean lists ready for use. It also verifies if your rules are even structurally sound, flagging errors before they break your calendar logic. Need to explain the rule to a non-technical manager? Use its summary feature; it translates deep technical patterns into plain language. When integrating this capability with Vinkius, your AI agent gets access to specialized scheduling knowledge, making complex calendar data instantly manageable. ## Tools ### expand_occurrences Calculates and returns a list of specific occurrence dates based on an RRULE string within a given date range. ### get_rrule_summary Generates a plain English summary that explains the meaning of a complex recurrence rule. ### validate_rrule Checks and confirms whether an input RRULE string follows proper calendar syntax standards. ## Prompt Examples **Prompt:** ``` I need all dates for a training session that runs every Monday, Wednesday, and Friday from January 20th through February 15th. ``` **Response:** ``` **Occurrences Found:** * January: 22nd, 23rd, 24th, 29th, 30th * February: 1st, 2nd, 5th, 6th, 7th, 12th, 13th, 14th These dates are calculated based on the 'weekly M/W/F' pattern within your requested window. Let me know if you need to adjust the start or end month. ``` **Prompt:** ``` Is this rule correct: FREQ=MONTHLY;BYDAY=2TH? What does it mean? ``` **Response:** ``` **Validation Status:** Valid This rule means 'The second Thursday of every single month.' It's a standard, recognized pattern. You can trust it for scheduling. ``` **Prompt:** ``` Explain this schedule: FREQ=YEARLY;BYMONTH=12;BYMONTHDAY=25, EXDATE=RDATE:2024-12-25 ``` **Response:** ``` **Plain English Summary:** This event happens yearly on December 25th. However, the date in 2024 has been manually removed from the schedule (it's an exclusion). *Next expected occurrence: December 25th of next year.* ``` ## Capabilities ### Calculate specific occurrence dates The MCP takes a recurrence rule and calculates every single date the event must happen within a specified start and end window. ### Validate calendar rule syntax It checks an RRULE string to make sure the structure is correct, preventing errors before you try to use the data. ### Summarize complex rules into plain English The MCP translates dense technical recurrence patterns into simple, human-readable descriptions of what the schedule means. ## Use Cases ### Determining Quarterly Board Meeting Dates A user needs to know all the dates for a meeting that happens quarterly on the last Friday. They ask their agent, and it uses `expand_occurrences` to provide a clean list of specific future dates. ### Checking Legacy System Data Integrity A data engineer receives 50 old event records with different recurrence rules. Instead of manually checking them all, they use `validate_rrule` on the entire batch to pinpoint which strings are technically broken. ### Explaining a Client's Complex Subscription Cycle A sales rep needs to explain how a subscription repeats every 3 months and is excluded in August. They run `get_rrule_summary`, and the agent delivers a simple, non-technical explanation for the client. ## Benefits - Stop guessing dates. Use `expand_occurrences` to get a precise, confirmed list of every event date within your required window. - Eliminate calendar errors before they happen. Run `validate_rrule` to guarantee that any recurrence string you work with is syntactically correct. - No more jargon. The MCP lets your agent run `get_rrule_summary`, instantly translating complex technical rules into language anyone can understand. - It handles advanced logic like exclusions (EXDATE) and additions (RDATE), ensuring your calculated dates are comprehensive and accurate. - The ability to process varied patterns, including BYDAY and BYMONTHDAY, means it works for nearly every type of repeating schedule you encounter. ## How It Works The bottom line is, it takes calendar jargon and gives you actionable, error-proof date information. 1. First, you pass the recurring event rule (the RRULE string) and the date range to your AI agent. 2. The MCP processes this data, using its tools to either calculate all dates, validate the syntax, or generate a clear summary based on your request. 3. Your agent receives structured output—either an accurate list of specific dates, confirmation that the rule is valid, or a simple English explanation. ## Frequently Asked Questions **How does Recurring Event Expander handle complex recurring schedules?** It calculates difficult patterns like 'the third Monday, excluding holidays' into concrete dates. You just provide the rule and a date range, and it outputs every single day that event is scheduled to happen. **Can I use Recurring Event Expander if my schedule pattern isn't perfect?** Absolutely. Before calculating anything, you can run a validation check on the rule itself. This tells you instantly if there are any structural errors in your calendar data that need fixing. **What happens if I don’t understand the technical recurrence rules?** The MCP has a summary tool that translates jargon into plain English. You give it the complex string, and it tells you exactly what the schedule means to a non-technical person. **Is Recurring Event Expander limited to specific types of calendars?** No. It adheres to the global RFC 5545 standard for recurrence rules, meaning it handles virtually every established calendar pattern used across professional scheduling tools. **Does this MCP work with dates from different time zones?** The tool focuses on date calculation based on the provided range. While proper timezone handling is key for final display, the core recurrence logic works reliably once you define your operational window.