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 capability 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.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Recurring Event Expander to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn complex recurrence rules into concrete date lists.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Recurring Event Expander.

01
Get rrule summary
Generates a human-readable summary of an RRULE
02
Validate rrule
Validates the syntax of an RRULE string
03
Expand occurrences
Expands an RRULE string into a list of occurrence dates within a window

One connector, every AI

Recurring Event Expander works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Recurring Event Expander to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

692ms average. Fast in production.

Recurring Event Expander is checked daily against the live service.

Daily averagePeak 839ms

Oct 3Today

Fastest day: 556ms
Slowest day: 839ms
14-day trend: Improving-7%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Recurring Event Expander, so you can see the experience inside your AI.

It does not authenticate your account with Recurring Event Expander. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Recurring Event Expander Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_yVWFO0rxR1OltATuNurj9QMd79zpTAItVWLQlFuA/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Recurring Event Expander capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "recurring-event-expander-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_yVWFO0rxR1OltATuNurj9QMd79zpTAItVWLQlFuA/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Recurring Event Expander in Claude and other AIs

See all the AI clients this connector works with ↑

FAQ

Questions Recurring Event Expander owners ask.

01
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'.
02
How can I verify if my rule is valid?
You can use the validate_rrule capability to check your RRULE string for structural integrity and compliance with the iCalendar standard.
03
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.

Explore

More in Scheduling

Connect Recurring Event Expander to Claude, Cursor, ChatGPT & more

Connect Recurring Event Expander to ChatGPT and Claude

Your AI does the work. We keep it safe and sound.