# Calendar event (.ics) generator

Create a valid iCalendar (.ics) file for one event, with optional reminder and repeat rule, ready to import.

- Endpoint: `POST https://setget.net/v1/tools/ics-event` with JSON `{"input": {...}}`
- MCP: `run_tool` with `slug` = `ics-event`
- Page: https://setget.net/tools/ics-event

## Inputs

- `title` (required, string): Name of the event.
- `start` (required, string): Start: a date (2026-03-14) for a whole-day event, or a date and time (2026-03-14T09:30).
- `end` (optional, string): End, in the same form as the start. For whole-day events this is the last day. Leave out to use the duration.
- `duration_minutes` (optional, integer, range 1..525600): Length in minutes, used when there is no end. Defaults to 60.
- `time_zone` (optional, string, one of `utc`, `floating`, default `"utc"`): utc writes exact times in UTC (an offset such as +01:00 is converted). floating keeps the clock time in whatever zone the viewer is in, and ignores any offset.
- `location` (optional, string): Where it takes place.
- `description` (optional, string): Notes for the event. Line breaks are kept.
- `url` (optional, string): A link for the event, such as a meeting address.
- `reminder_minutes` (optional, integer, range 0..40320): Show a reminder this many minutes before the start.
- `repeat` (optional, string, one of `none`, `daily`, `weekly`, `monthly`, `yearly`, default `"none"`): How often the event repeats.
- `repeat_count` (optional, integer, range 1..1000): Total number of occurrences when repeating.
- `repeat_until` (optional, string): Last date (2026-12-31) on which the event may repeat. Use this or repeat_count, not both.
- `uid` (optional, string): Unique ID of the event. Derived from the content when left out, so the same input gives the same file.
- `dtstamp` (optional, string): Creation time to record, as UTC (2026-03-01T12:00:00Z). Defaults to the event start.

## Example 1

```json
{"input":{"title":"Project kick-off","start":"2026-03-14T09:30","duration_minutes":45,"location":"Room 2, Main St","reminder_minutes":15}}
```

Result:

```json
{"text":"BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:-//SetGet//Event generator//EN\r\nCALSCALE:GREGORIAN\r\nMETHOD:PUBLISH\r\nBEGIN:VEVENT\r\nUID:87bf7650becd7028d0463f3a@setget.net\r\nDTSTAMP:20260314T093000Z\r\nDTSTART:20260314T093000Z\r\nDTEND:20260314T101500Z\r\nSUMMARY:Project kick-off\r\nLOCATION:Room 2\\, Main St\r\nBEGIN:VALARM\r\nACTION:DISPLAY\r\nDESCRIPTION:Project kick-off\r\nTRIGGER:-PT15M\r\nEND:VALARM\r\nEND:VEVENT\r\nEND:VCALENDAR\r\n","filename":"project-kick-off.ics","uid":"87bf7650becd7028d0463f3a@setget.net"}
```

## Example 2: A whole-day event over five days, repeating yearly

```json
{"input":{"title":"Team holiday","start":"2026-07-06","end":"2026-07-10","repeat":"yearly","repeat_count":3,"uid":"holiday-2026@example.com"}}
```

Result:

```json
{"text":"BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:-//SetGet//Event generator//EN\r\nCALSCALE:GREGORIAN\r\nMETHOD:PUBLISH\r\nBEGIN:VEVENT\r\nUID:holiday-2026@example.com\r\nDTSTAMP:20260706T000000Z\r\nDTSTART;VALUE=DATE:20260706\r\nDTEND;VALUE=DATE:20260711\r\nRRULE:FREQ=YEARLY;COUNT=3\r\nSUMMARY:Team holiday\r\nEND:VEVENT\r\nEND:VCALENDAR\r\n","filename":"team-holiday.ics","uid":"holiday-2026@example.com"}
```

**Which calendars open the file?** Google Calendar, Apple Calendar, Outlook and most others import .ics files. Save the text as event.ics.

**Why is the end date one day later in the file?** iCalendar stores the end of a whole-day event as the day after the last day. You enter the last day; the file follows the standard.

**What time zone are times in?** With "utc", a time without an offset is taken as UTC, and a time such as 09:30+01:00 is converted. With "floating", 09:30 means 09:30 wherever the viewer is.
