Calendar event (.ics) generator

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

Input

Name of the event.
Start: a date (2026-03-14) for a whole-day event, or a date and time (2026-03-14T09:30).
End, in the same form as the start. For whole-day events this is the last day. Leave out to use the duration.
Length in minutes, used when there is no end. Defaults to 60.
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.
Where it takes place.
Notes for the event. Line breaks are kept.
A link for the event, such as a meeting address.
Show a reminder this many minutes before the start.
How often the event repeats.
Total number of occurrences when repeating.
Last date (2026-12-31) on which the event may repeat. Use this or repeat_count, not both.
Unique ID of the event. Derived from the content when left out, so the same input gives the same file.
Creation time to record, as UTC (2026-03-01T12:00:00Z). Defaults to the event start.

Result

Fill in the input and press Run.

Your input is processed in memory and then discarded. It is not stored or logged. Even so, don't paste live passwords or keys into any online tool.

Use it from code or an agent

curl -s https://setget.net/v1/tools/ics-event \
  -H 'Content-Type: application/json' \
  -d '{"input":{"title":"Project kick-off","start":"2026-03-14T09:30","duration_minutes":45,"location":"Room 2, Main St","reminder_minutes":15}}'
import json, urllib.request

body = {'input': {'title': 'Project kick-off', 'start': '2026-03-14T09:30', 'duration_minutes': 45, 'location': 'Room 2, Main St', 'reminder_minutes': 15}}
request = urllib.request.Request("https://setget.net/v1/tools/ics-event", json.dumps(body).encode(),
                                 {"Content-Type": "application/json"})
print(json.load(urllib.request.urlopen(request))["result"])
const response = await fetch("https://setget.net/v1/tools/ics-event", {
  method: "POST",
  headers: {"Content-Type": "application/json"},
  body: JSON.stringify({"input":{"title":"Project kick-off","start":"2026-03-14T09:30","duration_minutes":45,"location":"Room 2, Main St","reminder_minutes":15}}),
});
console.log((await response.json()).result);
Tool: run_tool
Arguments:
{
  "slug": "ics-event",
  "input": {
    "title": "Project kick-off",
    "start": "2026-03-14T09:30",
    "duration_minutes": 45,
    "location": "Room 2, Main St",
    "reminder_minutes": 15
  }
}
{
  "input": {
    "title": "Project kick-off",
    "start": "2026-03-14T09:30",
    "duration_minutes": 45,
    "location": "Room 2, Main St",
    "reminder_minutes": 15
  }
}

Endpoint: POST /v1/tools/ics-event. Over MCP: run_tool with slug: "ics-event". Machine-readable: input schema, Markdown. Connect an agent.

Inputs

NameTypeRequiredWhat it does
title string yes Name of the event.
start string yes Start: a date (2026-03-14) for a whole-day event, or a date and time (2026-03-14T09:30).
end string no 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 integer no Length in minutes, used when there is no end. Defaults to 60. From 1 to 525600.
time_zone string no 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. One of: utc, floating. Default: "utc".
location string no Where it takes place.
description string no Notes for the event. Line breaks are kept.
url string no A link for the event, such as a meeting address.
reminder_minutes integer no Show a reminder this many minutes before the start. From 0 to 40320.
repeat string no How often the event repeats. One of: none, daily, weekly, monthly, yearly. Default: "none".
repeat_count integer no Total number of occurrences when repeating. From 1 to 1000.
repeat_until string no Last date (2026-12-31) on which the event may repeat. Use this or repeat_count, not both.
uid string no Unique ID of the event. Derived from the content when left out, so the same input gives the same file.
dtstamp string no Creation time to record, as UTC (2026-03-01T12:00:00Z). Defaults to the event start.

Examples

Input
{
  "title": "Project kick-off",
  "start": "2026-03-14T09:30",
  "duration_minutes": 45,
  "location": "Room 2, Main St",
  "reminder_minutes": 15
}
Result
{
  "text": "BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:-//SetGet//Event generator//EN\r\nCALSCALE:GREGORIAN\r\nMETHOD:PUBLISH\r\nBEGIN:VEVENT\r\nUID:[email protected]\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": "[email protected]"
}

A whole-day event over five days, repeating yearly

Input
{
  "title": "Team holiday",
  "start": "2026-07-06",
  "end": "2026-07-10",
  "repeat": "yearly",
  "repeat_count": 3,
  "uid": "[email protected]"
}
Result
{
  "text": "BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:-//SetGet//Event generator//EN\r\nCALSCALE:GREGORIAN\r\nMETHOD:PUBLISH\r\nBEGIN:VEVENT\r\nUID:[email protected]\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": "[email protected]"
}

Questions

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.