Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.
LLMs are bad at two humble things: knowing what time it is now, and doing timezone arithmetic. Models have no clock, and timezone conversion — with its daylight-saving edge cases and half-hour offsets — is exactly the kind of fiddly rule-following they fumble while sounding confident. The Time MCP server fixes both with two tools and no configuration.
get_current_time returns the actual current time in any IANA timezone ("America/New_York", "Asia/Kolkata"), which grounds every "what time is it in…" and "how long until…" question in reality. convert_time translates a time between zones with DST handled by a real timezone database rather than the model's recollection of when clocks change.
That sounds trivial until you schedule across continents. "Find a slot that's reasonable for Sydney, Berlin and San Francisco" involves three DST regimes; letting a model freestyle it produces meetings at 3 a.m. The server makes those conversions boringly correct, which is the only kind of correct that matters for calendars.
It's a tiny Python server from the official reference set, runs via uvx mcp-server-time, and is the sort of thing you install once and forget — until you notice your assistant has quietly stopped being wrong about time. Pairs naturally with calendar, email and scheduling servers, which all become more trustworthy when the time math underneath them is real.
Two tools, but a few sharp edges are worth having in mind before you trust an answer blindly:
America/New_York, not "EST". Abbreviations are ambiguous (there is more than one CST in the world) and get rejected rather than guessed at.convert_time takes a 24-hour time of day rather than a full date, so it resolves DST against today. For a meeting that sits on the other side of a clock change, state the date in your prompt and check the result.--local-timezone Europe/Berlin, or whichever zone is yours, when launching the server.Meeting slots across multiple DST regimes computed correctly instead of confidently wrong.
Deadlines, countdowns and 'how long ago' questions answered against a real clock.
Convert UTC log times to local zones accurately while debugging incidents.
| Tool | What it does |
|---|---|
| get_current_time | Current time in any IANA timezone |
| convert_time | Convert a time between timezones with DST handled correctly |
{
"mcpServers": {
"time": {
"command": "uvx",
"args": ["mcp-server-time"]
}
}
}Python 3.10+ with uv. Nothing else — no accounts, no keys.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.