LabscoMCP early access ↗
TakanariShimboMCP SERVER

DateTime

The current date and time in the format and timezone you configured once — ISO, Unix, human-readable, or your own strftime string.

by TakanariShimbo ↗Time, Dates & CalculationCommunity

LABSCO SUMMARY

Configured once, not argued about per call.

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.

What it is

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.

What you get

  • 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

Requirements

Nothing — no account, no key, no network. Launch with uvx takanarishimbo-datetime-mcp-server; the package is takanarishimbo-datetime-mcp-server (version 0.3.0) 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.

Setup effort

One command — uvx takanarishimbo-datetime-mcp-server