authProfile
Main user identity.
LABSCO 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
USE CASES
01
Asking what today looks like
Get the agenda and the day's tasks together, already ordered with the starred ones first.
02
Capturing a task mid-conversation
Create it as it comes up, rather than switching to the planner and losing the thread.
03
Clearing things off the list
Mark tasks done as you finish them, and re-open one you closed too early.
04
Seeing what is coming and what has no date
Read the upcoming weeks and the unplanned pile separately, which is the split that makes planning possible.
05
Looking up who an address belongs to
Resolve the email address to the contact that owns it before you draft anything.
06
Pulling up a note you wrote
List the pages and read the one you need, without leaving the conversation.
18 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
calendarAll
All calendars.
calendarGet
A calendar.
eventDay
The events on a given day.
eventGet
An event.
eventTimeline
Agenda view for a day.
pageAll
All pages.
pageGet
Get a page.
peopleByEmail
The potential contact owning this email address.
peopleGet
The contact with the given id.
taskComplete
Complete a task.
taskCreateSimple
Create a task (simplified for MCP).
taskDay
Tasks of a day sorted by: starred < default < (completed or ignored).
taskGet
A task.
taskUncomplete
Uncomplete a task.
taskUnplanned
Unplanned tasks.
taskUpcoming
Non-allocated organized by week and sorted alphabetically.
taskUpdate
Patch a task.
BEFORE YOU INSTALL
What to know first
Tools you get
18 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Moderate Standing cost
Rated by the size of the 18 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"routine-mcp-server": {
"command": "npx",
"args": [
"routine-mcp-server"
]
}
}
}npx
TERMINAL
npx routine-mcp-server
