Summary
One tool that closes the gap between the model's guess at the date and the real one.
A model has no clock, and the failures that follow are quiet ones — an interval computed from the wrong day, a deadline judged against training-time. The datetime:// resource is the reason to keep it around after the novelty passes: it answers for any zone, not just the one the server happens to sit in.
What it is
A small server that answers what time it is — as a tool for the system timezone, and as a datetime:// resource for any other.
What you get
- get_current_time returns the current local time in the system timezone
- A datetime:// URI scheme for any zone — datetime://Europe/London/now, datetime://America/New_York/now, datetime://Africa/Freetown/now
- Nothing else: no calendar, no scheduling, no state
Requirements
Uvx and the MCP-timeserver package — one entry in the client config, no key, no account, no configuration.
Setup effort
One command — uvx MCP-timeserver