get_current_timeLABSCO 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
USE CASES
01
Getting the model to work from today's date
It reads the real clock instead of assuming a date from training.
02
Answering what time it is somewhere else
Ask through the datetime:// resource for that zone rather than doing offset arithmetic.
03
Computing how long ago something happened
Anchor the arithmetic to the actual current time so the interval comes out right.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation. Beyond the one tool, the server exposes a datetime:// resource that returns the time in any zone.
Requires
uvx on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"MCP-timeserver": {
"command": "uvx",
"args": [
"mcp-timeserver"
]
}
}
}uvx
TERMINAL
uvx mcp-timeserver
