Yandex Calendar MCP server over CalDAV

yandex-calendar-mcp

A Yandex Calendar MCP server over CalDAV: reading the schedule, creating and editing events, invitations with real email delivery

  • 1 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Adding or removing an attendee sends a real invitation or cancellation email that cannot be recalled
  • Deleting events is irreversible on Yandex's side, though a local trash copy remains
All reasons and checks
Russian stack

platonking/yandex-calendar-mcp

Install

Services

Manual install

pip install -r requirements.txt

Installs dependencies, including tzdata.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Adding or removing an attendee sends a real invitation or cancellation email that cannot be recalled
  • Deleting events is irreversible on Yandex's side, though a local trash copy remains

This is third-party code. Review the repository files before installing.

What it does

The server gives an agent read and write access to Yandex Calendar over the CalDAV protocol. It reads events for a period up to 92 days across all calendars or one, expands recurring events into concrete dates, marks attendees with their reply status, and names the time zone explicitly in every response. For writes it creates one-off and recurring events, moves and renames them, edits a single day of a series via RECURRENCE-ID or the whole series, invites and removes attendees, and replies to invitations from others. Every write is verified by reading it back from the server, and if Yandex silently failed to apply a change, the server honestly reports failure instead of a false success. Before every delete and update, a full copy of the event is saved to YANDEX_TRASH_DIR as an ics file, and deletion additionally checks the event's title against the passed id to avoid erasing the wrong one. Adding or removing an attendee sends a real invitation or cancellation email through Yandex, which cannot be recalled.

Who it is for. For people who keep their schedule in Yandex Calendar and want to manage events and invitations from an agent chat.

Good fit when

  • You want to read and plan Yandex Calendar events from an agent
  • You care about every write being verified by an actual read, not trusting the server's response
  • You need correct handling of recurring events and time zones

Not a fit when

  • You do not want the agent able to send real invitation emails to attendees on your behalf
  • You need to edit someone else's event as if you were the organizer: the server only allows replying to an invitation, not editing someone else's event

Example request

Move the team meeting to Friday at 3pm and add the new hire to the attendees

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_USERNAME required
An address like name@yandex.ru
YANDEX_PASSWORD required, secret
A Yandex app password, not the account password
YANDEX_TRASH_DIR
The folder for ics copies of changed and deleted events

Limitations

You need a Yandex app password for CalDAV; a regular account password does not work. It needs Python 3.10 and the tzdata package, since slim Linux images often ship without a time zone database. Invitations and cancellations are sent as real emails and cannot be recalled. Deleting or editing someone else's event as if you were the organizer is impossible: Yandex silently rejects such edits, and the server detects this and refuses upfront.

How to disable. Remove the yandex-calendar entry from your MCP client configuration.

FAQ

Can a sent invitation be recalled?

No, Yandex sends a real email when an attendee is added or removed, and that cannot be undone.

What protects against deleting the wrong event?

The delete_event tool checks the event's id against the passed title and refuses on a mismatch, and saves a copy to YANDEX_TRASH_DIR before deleting.

How is the Yandex Calendar MCP over CalDAV different from API-based integrations?

The server reads and writes Yandex Calendar over CalDAV. It reads events for up to 92 days across all calendars or one, expands recurring events into concrete dates, creates and edits events and sends invitations with real emails.

Can I recall a sent invitation and what protects against deleting the wrong event?

Attendees can be removed from an event later, and Yandex sends the cancellations by mail itself. Before deleting, check the event identifier in the agent answer. Install with pip install -r requirements.txt, a Yandex app password is needed. Risk is high.

Discussion

No questions or reviews yet.

Yandex Calendar MCP server

Яндекс Календарь MCP для Claude

Russian stack

An MCP server for Yandex Calendar: view, create and delete events using an app password

MCP serverExtended access5Repository stars

Yandex Calendar plugin for Codex

Yandex Calendar для Codex

Russian stack

An unofficial local Yandex Calendar MCP plugin for Codex over CalDAV, with no intermediary cloud server

PluginBroad access
Russian stack

A small test Yandex Calendar MCP server over CalDAV: upcoming events, event creation and deletion with no confirmation step

MCP serverBroad access
Russian stack

A Yandex Calendar MCP server over CalDAV with a separate CLI for setup and app-password verification

MCP serverBroad access
Russian stack

A skill pack for Yandex 360: Mail, Calendar, Contacts, Directory, Telemost, Disk, Forms and Tracker

SkillBroad access12Repository stars

README in short

The README details read and write capabilities, a table of six tools, three layers of delete protection, a title check, a trash with ics copies, and a mandatory choice between one day of a series and the whole series, separately explains why you cannot edit someone else's event as its organizer, and honestly warns that invitations are sent as real, unrecallable emails.

README badge

Report a problem