Summary
The model stops guessing what time it is.
What it takes off you is the correction afterwards: a model has no clock, so "next Tuesday", "three hours ago" and "which week are we in" get answered from a call rather than from training data — in whichever timezone you name.
What it is
A small time server. Six calls cover the questions a model cannot answer on its own: what time it is now, and how one representation of a time relates to another.
What you get
- The current date and time, in the format and the timezone you ask for
- How far a given time is from now
- A Unix timestamp in milliseconds for a time you name, or for now
- The same instant converted between two timezones
- The number of days in a month, defaulting to the current one
- The week number of the year and the ISO week number
Requirements
Npx on your PATH, and nothing else. It runs as a local process, so the clock it reads is that machine's unless you name a timezone in the call.
Setup effort
One command — npx -y time-mcp