# Recurring Event Expander MCP for AI Agents AI Agent Connect

> Recurring Event Expander expands RFC 5545 RRULE strings into concrete lists of occurrence dates. It takes complex recurrence patterns, like "every third Friday of the month," and turns them into a precise list of dates for your agent to process. It handles exclusions and specific additions, making it the go-to tool for any scheduling automation that needs to deal with real-world calendar logic.

## Overview
- **Category:** scheduling
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_yVWFO0rxR1OltATuNurj9QMd79zpTAItVWLQlFuA/ai-agent-connect
- **Tags:** rrule, rfc5545, calendar, scheduling, dates, automation

## Description

Dealing with recurrence rules is a mess. If you're trying to figure out when a recurring meeting actually happens or how many instances of an event fall into a specific month, you usually have to write a bunch of boilerplate code to parse the RFC 5545 standard. This Connector takes that weight off your shoulders. It lets your AI client do the heavy lifting of calculating dates based on complex logic like specific days of the week, month-day rules, and even specific position sets.

You can use this to build smarter scheduling tools or automate complex holiday rotations without getting bogged down in the math of calendar logic. It's a core part of the Vinkius catalog, designed to bridge the gap between a raw string of text and a list of actual dates your agent can act on. Instead of your agent hallucinating dates, it gets a precise list of occurrences. It also handles the tricky stuff, like skipping specific dates or adding one-off instances, so your automation doesn't break when the real world gets messy.

## Tools

### expand_occurrences
Converts an RRULE string into a list of concrete dates within a set window. Use this to get every date for a recurring event.

### get_rrule_summary
Provides a human-readable explanation of what a complex recurrence rule actually means. This helps you understand technical strings.

### validate_rrule
Checks a recurrence string to ensure it follows the correct RFC 5545 syntax. Use this to catch errors before they break your code.

## Prompt Examples

**Prompt:** 
```
Expand this rule: 'FREQ=WEEKLY;BYDAY=MO,WE,FR' from 2024-01-01 to 2024-01-15.
```

**Response:** 
```
The occurrences for the period are:

* 2024-01-01
* 2024-01-03
* 2024-01-05
* 2024-01-08
* 2024-01-10
* 2024-01-12
* 2024-01-15
```

**Prompt:** 
```
Is this RRULE syntax correct: 'FREQ=MONTHLY;BYDAY=2TH'?
```

**Response:** 
```
Yes, the syntax is valid. 

This rule represents an event occurring on the **second Thursday of every month**.
```

**Prompt:** 
```
What does this rule mean in plain English: 'FREQ=YEARLY;BYMONTH=12;BYMONTHDAY=25'?
```

**Response:** 
```
This rule represents an event occurring on **December 25th every year**.
```

## Capabilities

### List every specific date
Convert a recurrence rule into a clean list of dates within a chosen timeframe.

### Check rule syntax
Verify that an RRULE string follows the correct RFC 5545 standard.

### Summarize complex rules
Get a plain English explanation of what a technical recurrence string actually means.

### Handle date exclusions
Account for specific dates that should be skipped in a recurring series.

### Calculate position sets
Process rules that rely on specific positions like the second Tuesday of the month.

## Use Cases

### Shift Planning
An HR bot needs to know all shift dates for "every other Saturday" to check for overlaps in a staff schedule.

### Project Milestones
A project manager wants to see all recurring "Sync" dates for the next 6 months to plan resource allocation.

### Holiday Logic
An automation script needs to identify all company holidays that fall on a weekday for a specific year.

### Booking Systems
A clinic needs to expand a "monthly" appointment rule to see all available dates for a specific month.

## Benefits

- Stop manual date calculation. Use expand_occurrences to get every date in a range without doing the math yourself.
- Verify rule accuracy. Use validate_rrule to catch syntax errors in your calendar data before they cause issues.
- Improve agent readability. Use get_rrule_summary to let your agent explain complex rules in plain English.
- Handle messy exceptions. The Connector manages EXDATE and RDATE so your agent knows exactly which dates to skip.
- Scale scheduling logic. Support for BYDAY and BYMONTHDAY makes it easy to handle complex recurring patterns.
- Reduce hallucination. Your agent gets a precise list of dates instead of guessing the next occurrence.

## How It Works

The bottom line is it turns messy recurrence strings into usable date lists instantly.

1. Provide the RRULE string and your desired date range.
2. The Connector parses the logic and checks for validity.
3. You get a clean list of dates or a readable summary.

## Frequently Asked Questions

**What is the Recurring Event Expander MCP?**
It is a tool that takes complex recurrence rules (RRULEs) and turns them into a simple list of actual dates. This makes it much easier for your AI agent to understand and act on recurring schedules.

**Can it handle complex rules like 'every 2nd Tuesday'?**
Yes, it handles advanced logic including specific days of the week, month-day rules, and position sets like 'the second Tuesday'.

**Does the Recurring Event Expander MCP support date exclusions?**
Yes, it can handle exclusions (EXDATE) and additions (RDATE), ensuring your agent knows which specific dates to skip in a recurring series.

**How do I use it for calendar automation?**
You provide the recurrence string and a date range. The Connector returns a list of dates that your agent can then use to book meetings, check availability, or generate reports.

**Can it tell me what a weird RRULE string actually means?**
Yes, it can generate a human-readable summary of a technical recurrence string so you can verify what the rule actually does in plain English.

**Is this for RFC 5545 standards?**
Yes, it is specifically designed to parse and expand rules following the RFC 5545 standard, which is the standard for iCalendar files.

**What is an RRULE?**
An RRULE (Recurrence Rule) is a standard format defined in RFC 5545 used to describe recurring events, such as 'every Monday' or 'the last Friday of the month'.

**How can I verify if my rule is valid?**
You can use the `validate_rrule` tool to check your RRULE string for structural integrity and compliance with the iCalendar standard.

**Can I exclude specific dates from the expansion?**
Yes, when using `expand_occurrences`, you can provide a list of ISO 8601 timestamps in the `exdates` parameter to exclude them from the resulting list.