McpStamp Calendar

io.github.theluckystrikePublished by GitHub account theluckystrikev0.23.0Updated Nov 3, 2026

Read .ics calendar exports: events in a window, free slots, double bookings, new .ics files.

The publisher's own server: Events.Aero

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

McpStamp Calendar's hosted MCP server (mcp.zovo.one); no sign-in required; Streamable HTTP; 12 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
mcp.zovo.one
Last checked

Installation

In SourceWeft

  1. Open McpStamp Calendar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.theluckystrike%2Fcalendar-ics-reader-events-freebusy-conflicts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcpstamp-calendar": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/calendar"
    }
  }
}

README

mcp-calendar

Your calendar app can show you next Tuesday. It cannot tell you where your week actually went, which two things you said yes to at the same time, or how many billable hours last month's meetings were worth. This server reads the .ics file your calendar already exports and answers those questions: events in any window with recurring series expanded properly, merged busy blocks and the real free gaps inside your working hours, every double booking across work and personal calendars at once, a clean .ics of just the events you picked, and the exact time entry for a meeting you should have billed. No account is connected, nothing is synced, and the calendar file stays on your machine as plain text.

Built by theluckystrike.

In the official MCP Registry (io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts).

Listed on the AI Product Index - live remote endpoint at mcp.zovo.one/s/calendar, free tier, no signup.

[calendar demo]

Import the .ics your calendar exports, then ask what is on, when you are free, and what clashes, zero setup, all local.

60-second install

npm publish for @theluckystrike/mcp-calendar is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.

One-click (.mcpb): download calendar.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

(claude_desktop_config.json):

json
{  "mcpServers": {    "calendar": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-calendar"]    }  }}

Claude Code:

sh
claude mcp add calendar -- npx -y @theluckystrike/mcp-calendar

(.cursor/mcp.json):

json
{  "mcpServers": {    "calendar": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-calendar"]    }  }}

The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these four commands:

sh
git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-serversnpm installnpm run build -w packages/mcp-license -w servers/timezone -w servers/calendar

Then point your client's command at node with one arg: the absolute path to servers/calendar/dist/index.js.

To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.

Getting the .ics out of your calendar

AppWhere
Google CalendarSettings -> Import & export -> Export. You get a zip; import the .ics inside it.
Apple CalendarFile -> Export -> Export...
Outlook (desktop)File -> Save Calendar, format iCalendar (.ics)
Outlook / Microsoft 365 (web)Settings -> Calendar -> Shared calendars -> Publish, then use the ICS link (Pro)
Anything elseAny published feed URL ending in .ics, or webcal:// (Pro)

Then: ics_import {path: "~/Downloads/[email protected]", name: "work"}

Tools

ToolWhat it does
ics_importRead a .ics file (path), pasted contents (text) or a public feed (url, Pro) and keep it locally under a name. Importing the same name again replaces it.
calendars_listEvery imported calendar: name, source, event count, size, when it was imported.
events_listEvery event between two dates with recurring series expanded to real occurrences, sorted, in your own time zone. Each row carries an id.
events_searchEvents whose title, description, location, organizer or attendees contain a phrase.
free_busyMerged busy blocks and the free gaps inside your working hours, day by day. Events marked free/transparent do not count as busy.
conflictsEvery pair of events that overlap, with the overlap in minutes -- across all calendars, so a client call clashing with a school run is caught. A longer window is shortened to the free 31 days and answered, never refused.
next_eventThe next thing that has not started, and how long until it does.
event_exportWrite chosen events (by id, or a whole window) to a new .ics you can send. Times in UTC, so it lands correctly in any client.
event_to_time_entryTurn one meeting into the exact arguments for the time-tracker's entry_add, so a call becomes billable time without retyping it.
ics_forgetRemove one calendar and its local copy.
license_status / license_activateShow the tier; activate a Pro key offline.

Resource calendar://today gives today's schedule in one read. Prompt plan_my_day walks the whole loop: what is on, what clashes, where the free stretches are, and which finished meetings to bill.

What the parser handles

Written against real exports, not just the spec: line folding (CRLF, bare LF and bare CR, and folds that Exchange places inside a multi-byte character, which are rejoined on the bytes before decoding), \n \, \; \\ escaping, whole-day events with an exclusive DTEND, DURATION instead of DTEND, TZID and UTC times, floating times, RRULE for HOURLY, DAILY, WEEKLY, MONTHLY and YEARLY with COUNT, UNTIL (inclusive), INTERVAL, BYDAY including ordinals (2MO, -1FR), BYMONTHDAY, BYMONTH and BYSETPOS, EXDATE, RDATE, RECURRENCE-ID overrides (the moved instance replaces the original instead of appearing twice), STATUS:CANCELLED, TRANSP:TRANSPARENT, and VALARM blocks inside an event. An event it cannot read is skipped and counted rather than costing you the rest of the file.

FREQ=MINUTELY and FREQ=SECONDLY are deliberately not expanded: one such rule fills any window with thousands of occurrences and buries the rest of the week. Those events are listed at their first occurrence and the reason is said out loud. A rule with no COUNT and no UNTIL is expanded only as far as the window you asked for.

Exports written by this server keep whole-day events as DATE values, so a holiday leaves as the same day it arrived rather than a timed block on the day before in your machine's zone.

VTIMEZONE is deliberately ignored. A file's inline DST rules are only as fresh as the app that wrote it; the TZID is kept and every offset is computed from the ICU data inside your Node build instead, which is what keeps a weekly Warsaw 10:00 meeting at 10:00 local across the March clock change.

Free vs Pro

FreePro ($19 one-time)
Calendars kept2unlimited
Window per questionup to 31 daysany window
conflicts over a longer windowanswered for the first 31 days, cap namedany window
Events per export50unlimited
Import from a URL or webcal feed--yes
Everything elsefullfull

Get Pro, or $39 for every server in the suite, lifetime.

Privacy

Everything is local. The calendar file you import is copied to ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/calendar/ and read from there; deleting that directory resets the server. There is exactly one network call in the whole server, and only when you pass a url yourself: it fetches that address once, with a 12-second timeout, a 5 MB cap, and a refusal on loopback, private and cloud-metadata addresses. Nothing is uploaded, no account is linked, and licence keys verify offline.

Pairs with

  • mcp-timezone, this server reads its time zone and .ics engine from it: convert a meeting time, find slots across countries, write an invite.
  • mcp-time-tracker, event_to_time_entry hands it a finished meeting; it tracks and reports the hours.
  • mcp-invoice, turn those tracked hours into a numbered invoice.
  • office-suite, several servers behind one install, one config entry.

FAQ

No. There is no OAuth, no token and no sync. You export a file (or paste a public feed URL on Pro) and it is read locally. That also means an import is a snapshot: re-import when the calendar has moved on.

Yes, and that is most of the code. A weekly series is expanded on the wall clock, so a Warsaw 10:00 meeting stays 10:00 through the DST change rather than drifting to 11:00. Monthly on the 31st skips February instead of rolling into March, UNTIL includes the occurrence that falls exactly on it, and a single moved instance replaces the original.

It is not: RFC 5545 makes DTEND exclusive for a whole-day event, so 1--3 June means the 1st and the 2nd. This server follows the spec, which is what your calendar app does too.

It writes .ics files with event_export, which you can import anywhere. It never modifies the calendar it read.

5 MB, which is a few thousand events. Export a narrower date range if a full history is bigger than that.

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Source: servers/calendar/README.md at commit 6535b33

Tools

12

license_status

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Takes no parameters.

license_activate

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Parameterskeyrequired

ics_import

Import a calendar (.ics)

Call this tool to read a calendar export and keep it under a name. Give path (.ics file), text (contents), or url (public .ics/webcal feed; Pro). Google, Apple, Outlook exports read. Re-importing a name replaces it.

Parametersurlnamerequiredpathtext

calendars_list

List imported calendars

List imported calendars: name, event-definition count, size, source, import time and free-tier use of the 2 slots. It also names stored .ics files with no calendar row. With none it prints the export steps.

Takes no parameters.

events_list

List events in a window

Every event between two dates, recurring expanded to occurrences, sorted by start. Times shown in your zone (profile's, else this machine's) unless zone passed. Each id works for event_export or event_to_time_entry.

Parameterstorequiredfromrequiredzonecalendar

free_busy

Busy blocks and free windows

Merged busy blocks and the free gaps inside your working hours over a day range. Events marked free do not count; whole-day events block the day. Free: 31 days. Use conflicts for overlapping pairs.

Parameterstorequiredfromrequiredzonework_endcalendarswork_start

conflicts

Find double bookings

Find double bookings: every PAIR of timed events that overlap, with the minutes they collide, across all calendars unless you name one. Whole-day events are reported apart. Free: 31 days. free_busy shows gaps.

Parameterstorequiredfromrequiredcalendar

next_event

Next event

The first event not yet started, within the next 366 days, across every imported calendar or one you name. Returns title, times in your zone, how long until it starts, location, attendees and its id.

Parameterscalendar

event_export

Export events to a .ics file

Call this tool to write chosen events to a new .ics file you can send or import elsewhere. Pass either ids (from events_list) or a from/to window. Times are written in UTC so the file lands correctly in any client.

Parameterstoidsfromcalendarout_pathrequired

event_to_time_entry

Turn a meeting into a time entry

Take one event and return the exact arguments for the time-tracker's entry_add, so a meeting that already happened becomes billable time without retyping it. Writes nothing: pass the JSON straight to entry_add.

Parametersrateprojectrequiredcurrencyevent_idrequired

ics_forget

Forget a calendar

Remove one imported calendar by name and delete this server's local copy of its .ics, freeing a slot. Your own calendar and the source file are untouched. ics_import replaces a name in place.

Parametersnamerequired

Version history

4
  1. v0.23.0LatestNov 3, 2026
  2. v0.22.6Oct 14, 2026
  3. v0.22.0Sep 17, 2026
  4. v0.21.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Events integrations