This does not try to be a Dooray client — it adds schedule entries, and the calendar it writes to is decided by configuration rather than by the model. That is a reasonable safety property for a write-only calendar tool, and it also means covering a second calendar means a second server entry.
A small Python MCP server that manages schedules through the Dooray API. It runs locally over stdio and is scoped to a single Dooray calendar, named by the credentials you give it.
Calendar events created in Dooray from a conversation: the server calls the Dooray API to add the schedule, sets the start and end times for you rather than requiring both explicitly, and carries location and description alongside the event.
A Dooray account with an API key. Three environment variables in a `.env` file: `DOORAY_API_KEY`, `DOORAY_MEMBER_ID` and `DOORAY_CALENDAR_ID` — the calendar ID is fixed per install, so one server covers one calendar. Python with a virtual environment, then `pip install -e .`; your client config names the interpreter in that virtual environment and the server script path. Smithery can install it for Claude Desktop in one command instead. MIT licensed.
One command plus a key — npx -y @smithery/cli install @mskim8717/dooray-mcp --client claude, then supply credentials