Skip to main content
AgentsUse

MCP server, by Model Context Protocol

Time MCP Server

Python MCP server that returns the current time in an IANA timezone and converts times between timezones.

stdio (local process)Checked 2026-10-07Config checked

Quick facts

Transport
stdio (local process)
Runs as
uvx (mcp-server-time)
Review state
Config checked against the official source. Facts checked 2026-10-07. Not locally tested by AgentsUse.

What it does

The time server answers current time questions and timezone conversions for a model. It uses IANA timezone names such as America/New_York and Europe/London, and it detects the system timezone automatically when no override is given.

A --local-timezone argument overrides the detected system zone. The Docker example passes LOCAL_TIMEZONE through the environment. Responses include the timezone, an ISO datetime, and a daylight saving flag, and conversions include the time difference.

It runs with uvx, pip, or Docker, and requires MCP Python SDK 1.x per the README.

Configuration

Run with uvx mcp-server-time, install with pip install mcp-server-time, or use the mcp/time Docker image.

MCP config (placeholders)
{
  "mcpServers": {
    "time": {
      "command": "uvx",
      "args": ["mcp-server-time"]
    }
  }
}

Source: https://github.com/modelcontextprotocol/servers/tree/main/src/time. Placeholders only. Replace them in your own environment, and never commit real keys to a repository.

Environment variableRequiredPurpose
LOCAL_TIMEZONEOptionalUsed in the Docker example to pass the local timezone into the container.

Verified tools and features

  • get_current_time Config checked

    Returns the current time for a required IANA timezone argument, with datetime and is_dst fields.

  • convert_time Config checked

    Converts an HH:MM time between source and target IANA timezones and returns the difference.

  • Automatic system timezone detection Config checked

    Detects the system timezone by default, with a --local-timezone override.

Security notes

Security notes
  • The server reads system time and timezone only. No filesystem writes, network calls or credentials are described.
  • Timezone names are inputs from the model. Invalid names will fail rather than widen access.
  • No API keys are required.

An MCP server runs with the permissions of the process you start it from. Scope credentials to the narrowest access the job needs, and review what the client will send before connecting anything sensitive.

Sources and freshness

Last checked 2026-10-07. Verification label: config checked, which means the configuration and feature list trace to the official source above. It does not mean AgentsUse ran the server. Spotted an error? Send a correction. Back to the MCP server index.