That is the trade against time servers that take a format argument on every call: you lose the flexibility, and you gain consistency — every timestamp in a session looks the same, because the model cannot choose differently on the second call. If you want Tokyo time in ISO form throughout, set it and stop thinking about it. If you need two formats in one session, this is the wrong shape and a per-call server is the right one.
A small Python MCP server that answers with the current date and time. A model has no clock, so anything that needs "now" needs a tool; this one is configured through environment variables rather than per call, so every answer comes back in the shape you set.
- The current time in the configured format — `get_current_time`
- Seven output formats via `DATETIME_FORMAT`: `iso`, `unix` seconds, `unix_ms` milliseconds, `human`, `date` only, `time` only, or `custom`
- A custom format built from Python strftime codes in `DATE_FORMAT_STRING`, defaulting to `%Y-%m-%d %H:%M:%S`
- Any timezone through `TIMEZONE`, defaulting to UTC — so a server configured for `Asia/Tokyo` answers in Tokyo time without the model doing offset arithmetic
Nothing — no account, no key, no network. Launch with `uvx takanarishimbo-datetime-mcp-server`; the package is `takanarishimbo-datetime-mcp-server` (0.3.0 in pyproject) over stdio. Configuration is entirely by environment variables in your client's config block, so changing the output format means editing that block and restarting the client rather than passing an argument.
One command — uvx takanarishimbo-datetime-mcp-server