LabscoMCP early access ↗
modelcontextprotocolMCP SERVER · OFFICIAL PROJECT

Time

Answer "what time is it there" and "when is that for me" from real IANA timezone data instead of the model's arithmetic.

by modelcontextprotocol ↗Time, Dates & Calculation✓ Anthropic

LABSCO SUMMARY

The scheduling arithmetic that models quietly get wrong, moved onto the timezone database.

Two tools, both narrow on purpose: what time is it in a zone, and what does this time become in another zone. Because it detects your system zone at startup, "what time is it now" and "convert 9:30 in Tokyo" both work without the conversation having to state where you are.

What it is

A two-tool server over the IANA timezone database: the current time in a named zone, and one clock time converted between two zones.

What you get

  • Current time in any IANA zone, addressed by name — America/New_York, Europe/London
  • A time in 24-hour HH:MM form converted from a source zone to a target zone
  • Your system timezone detected on startup, so a question that names no zone still resolves

Requirements

Nothing to authorize. Run it with uvx from the published package mcp-server-time, or pip install it and run python -m mcp_server_time; a Docker image, mcp/time, is published too. Pass --local-timezone to override the detected system zone.

Setup effort

One command — uvx mcp-server-time