Summary
Your planner's data, without the planner in front of you.
Because it talks to the app running on your machine, there is no API key and nothing leaves the desk — but the app has to be open for any of it to answer. The write surface is deliberately narrow: tasks can be created, changed and completed, while calendars, events, pages and contacts stay read-only.
What it is
A server for the Routine planner app. It reads calendars and events, the day's agenda, tasks in several views, pages and contacts, and writes to tasks — creating, patching, completing and re-opening them.
What you get
- All calendars, or one by identifier
- The events on a given day, one event in full, and an agenda view of the day
- The tasks for a day, ordered starred first, then the rest, then completed or ignored ones
- Upcoming tasks organised by week, and separately the ones with no date on them at all
- A task created, patched, completed or re-opened
- Pages listed and read
- A contact by identifier, or resolved from the email address it owns
- The signed-in user's identity
Requirements
The Routine desktop application running on the same machine — the server talks to it locally. Node to run the server. No key to paste.
Setup effort
One command — npx routine-mcp-server