
cal-scheduler
io.github.limeyPublished by GitHub account limeyv1.1.3Updated Oct 24, 2026
Timezone-correct CalDAV scheduling MCP server with validated recurrence and single-occurrence edits.
Overview
A local MCP server that lets an assistant read and write events on any CalDAV calendar with correct timezone and recurrence handling.
- What you can do
- Exposes a small, strict set of calendar tools: list, create, update and delete events, list, create and delete calendars, exclude or move a single occurrence of a recurring series, and mark an event done. It stores events zoned to a configured IANA timezone with TZID/VTIMEZONE, validates recurrence rules, and normalises UNTIL to UTC. A helper tool previews how a datetime will be interpreted without writing anything.
- When to use it
- Use it when an assistant should schedule against a CalDAV calendar and timezone correctness matters, for example recurring meetings that must keep their local wall-clock time across daylight-saving changes, or edits to one occurrence of a series. It is a validation and persistence layer, not a natural-language parser, so the agent phrases the request.
- Requirements
- Runs locally as a stdio subprocess; needs Python 3.11 or newer and the PyPI package cal-scheduler-mcp, typically installed with uv tool install or run with uvx. Configuration is by environment variables: CALDAV_BASE_URL is required, and CALDAV_USERNAME, CALDAV_PASSWORD and CAL_DEFAULT_TZ are optional. Network access to the CalDAV server is needed, and the host must pass these variables in its per-server env block.
Installation
In SourceWeft
- Open cal-scheduler in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
If you are an agent installing this MCP, read AGENTS.md first.
cal-scheduler
[cal-scheduler-mcp MCP server]
A thin, timezone-correct MCP server for scheduling against any CalDAV calendar. It gives an LLM agent a small, strict set of calendar tools and does the deterministic, fiddly parts of iCalendar correctly so the model doesn't have to.
It is not an NLP layer: the agent phrases the request, the server validates
it, rejects bad input loudly, and persists clean zoned .ics.
Why it exists
Most calendar tooling an LLM reaches for gets three things subtly wrong. cal-scheduler fixes them by construction:
- Stores zoned, not bare UTC. Events are written with
TZID/VTIMEZONE, so a weekly 9am stays 9am across a daylight-saving boundary instead of drifting an hour. Storing bare UTC is the classic cause of that drift. - Validates recurrence. It rejects an
RRULEwhose anchor contradicts it (e.g. a series starting on the 30th but set to repeat on the 1st), and normalisesUNTILto UTC under a zonedDTSTARTas RFC 5545 requires. - Does real single-occurrence edits. Exclude one instance (
EXDATE) or move one instance (RECURRENCE-ID) without disturbing the rest of the series — the operations naive wrappers tend to lack.
How it works
A small uv Python package that composes mature libraries rather than
implementing a calendar engine:
It runs as a stdio MCP server that an MCP host (Claude, an agent harness, etc.) spawns as a subprocess.
Install
Requires Python ≥ 3.11. The package is on PyPI as
cal-scheduler-mcp:
(or pip install cal-scheduler-mcp, uvx --from cal-scheduler-mcp cal-scheduler,
etc.)
For editable dev work, install from a clone:
Don't
uv add cal-scheduler-mcpfor the MCP —uv addwrites into whatever project you're sitting in, not into the tool environment. For an MCP server (spawned as a subprocess),uv tool installis the right shape.
Configure
All configuration is via environment variables:
Many MCP hosts strip inherited environment from stdio servers, so set these in the
host's per-server env block rather than relying on the ambient shell.
Example MCP host config
The MCP runs as a stdio subprocess that the host spawns. Many hosts strip
inherited PATH from that subprocess, so wire the uv run --directory
form rather than relying on the cal-scheduler shim being on the spawn
host's PATH:
/abs/path/to/cal-scheduler-mcp is the absolute path to a local clone of
this repo (see Install above).
If you installed from PyPI with uv tool install cal-scheduler-mcp, use the
installed shim directly:
Find the shim path with which cal-scheduler or uv tool list --show-paths.
Pair it with any CalDAV server. A simple self-hosted option is
Radicale (plain http://, no TLS needed for local use).
Tool surface
Events — list_events(start, end, [calendar]), create_event(summary, start, [end, calendar, description, location, rrule]), update_event(uid, …),
delete_event(uid, [calendar]), exclude_occurrence(uid, occurrence, [calendar]),
move_occurrence(uid, occurrence, new_start, [new_end, calendar]),
mark_done(uid, [calendar]) — tag an event done and record the timestamp.
Calendars — list_calendars, create_calendar(name), delete_calendar(name).
Helper — resolve_datetime(value) — preview how a datetime will be interpreted,
without writing anything.
The timezone rule (the whole point)
Every event is stored zoned to CAL_DEFAULT_TZ.
- A naive datetime (
2026-06-30T21:00) is assumed to be wall time in that zone, and the tool response says so ("assumed Pacific/Auckland wall time"). - An offset-qualified datetime (
…+12:00) is honoured as an instant and re-expressed in the zone — same wall clock when the offset matches, a correct conversion otherwise. - A date-only value (
2026-06-30) is an all-day event.
Develop
The unit tests cover the pure layers (timezone resolution, recurrence validation,
EXDATE/RECURRENCE-ID construction) and need no running CalDAV server. To exercise
the full stack end to end, point CALDAV_BASE_URL at a throwaway CalDAV account.
License
MIT © 2026 Robert Clark
Source: README.md at commit 0373f85
Tools
0Version history
1- v1.1.3LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts