A simple Yandex Calendar MCP server
mcp_yandex_calendar
A small test Yandex Calendar MCP server over CalDAV: upcoming events, event creation and deletion with no confirmation step
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- delete_calendar_event deletes an event with no confirmation and no backup
- create_calendar_event writes to the user's first calendar with no way to choose another
Install
Manual install
docker build -t mcp-yandex-calendar . && docker run -p 8088:8088 --env-file .env mcp-yandex-calendarBuild and run from the Dockerfile, port 8088.
This is third-party code. Review the repository files before installing.
What it does
A FastMCP-based server connects to Yandex Calendar over CalDAV via the caldav library and picks the user's first available calendar. It offers three tools: get_upcoming_events returns upcoming events for a given number of days as text or JSON, create_calendar_event creates an event from a title, date, time, duration and description, and delete_calendar_event deletes an event. The author calls the project a test build made to try containerizing an MCP server, and runs it in a Docker image on Ubuntu with port 8088 and the Europe/Moscow time zone. There are no extra checks before deletion, no confirmation step, and no event backup in the code.
Who it is for. For people who want a minimal, containerized Yandex Calendar MCP server example and are ready to extend it themselves.
Good fit when
- You want a small, easy-to-read Yandex Calendar MCP server example built on Python and caldav
- Basic view, create, delete operations are enough
- You want a ready Dockerfile for a containerized run
Not a fit when
- You need protection against accidental deletion: there is no confirmation, title check or backup in the project
- You need to work with several calendars: the server always picks the first one in the list
Example request
Show my upcoming Yandex Calendar events for the next 14 daysLimitations
The author explicitly calls the project a test. No license is stated. Deleting an event needs no confirmation and keeps no backup. The server always works with the first calendar in the user's list; there is no way to pick another. You need a Yandex app password of the Calendar type, not the account password.
How to disable. Stop the server container or process and remove it from your MCP client configuration.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_USERNAME required | An address like email@yandex.ru |
| YANDEX_PASSWORD required, secret | A Yandex app password of the Calendar type |
Security check
- delete_calendar_event deletes an event with no confirmation and no backup
- create_calendar_event writes to the user's first calendar with no way to choose another
README in short
The README is a step-by-step guide to creating a Yandex Calendar app password over CalDAV, with a warning not to use the main account password, and no description of the server's own tools.
FAQ
Does the server ask for confirmation before deleting an event?
No, delete_calendar_event deletes the event immediately, with no confirmation and no backup.
Can I choose which calendar it works with?
No, the server always connects to the first calendar in the list Yandex returns.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI