Skip to main content

Time MCP Server

A Model Context Protocol server that provides time and timezone conversion capabilities. This server enables LLMs to get current time information and perform timezone conversions using IANA timezone names, with automatic system timezone detection.

Source: https://github.com/modelcontextprotocol/servers/tree/main/src/time

Requires MCP Python SDK 1.x (mcp>=1.29.0,<2). SDK 2.0 renamed APIs this server uses. The port to v2 is in progress.

Available Tools

  • get_current_time - Get current time in a specific timezone or system timezone.

    • Required arguments:
      • timezone (string): IANA timezone name (e.g., 'America/New_York', 'Europe/London')
  • convert_time - Convert time between timezones.

    • Required arguments:
      • source_timezone (string): Source IANA timezone name
      • time (string): Time in 24-hour format (HH:MM)
      • target_timezone (string): Target IANA timezone name

A timezone name, here and in --local-timezone, must be an exact IANA key, case included: Europe/Warsaw is accepted and europe/warsaw is rejected on every platform, including macOS, whose case-insensitive filesystem would otherwise resolve it.

Installation

When using uv no specific installation is needed. We will use uvx to directly run mcp-server-time.

uvx mcp-server-time

Using PIP

Alternatively you can install mcp-server-time via pip:

pip install mcp-server-time

After installation, you can run it as a script using:

python -m mcp_server_time

Configuration

Configure for Claude.app

Add to your Claude settings:

Using uvx
{
  "mcpServers": {
    "time": {
      "command": "uvx",
      "args": ["mcp-server-time"]
    }
  }
}
Using docker
{
  "mcpServers": {
    "time": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "LOCAL_TIMEZONE", "mcp/time"]
    }
  }
}
Using pip installation
{
  "mcpServers": {
    "time": {
      "command": "python",
      "args": ["-m", "mcp_server_time"]
    }
  }
}

Configure for Zed

Add to your Zed settings.json:

Using uvx
"context_servers": [
  "mcp-server-time": {
    "command": "uvx",
    "args": ["mcp-server-time"]
  }
],
Using pip installation
"context_servers": {
  "mcp-server-time": {
    "command": "python",
    "args": ["-m", "mcp_server_time"]
  }
},

Configure for VS Code

For quick installation, use one of the one-click install buttons below...

Install with UV in VS Code Install with UV in VS Code Insiders

Install with Docker in VS Code Install with Docker in VS Code Insiders

For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).

Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.

Note that the mcp key is needed when using the mcp.json file.

Using uvx
{
  "mcp": {
    "servers": {
      "time": {
        "command": "uvx",
        "args": ["mcp-server-time"]
      }
    }
  }
}
Using Docker
{
  "mcp": {
    "servers": {
      "time": {
        "command": "docker",
        "args": ["run", "-i", "--rm", "mcp/time"]
      }
    }
  }
}

Configure for Zencoder

  1. Go to the Zencoder menu (...)
  2. From the dropdown menu, select Agent Tools
  3. Click on the Add Custom MCP
  4. Add the name and server configuration from below, and make sure to hit the Install button
Using uvx
{
    "command": "uvx",
    "args": ["mcp-server-time"]
  }

Customization - System Timezone

By default, the server automatically detects your system's timezone. You can override this by adding the argument --local-timezone to the args list in the configuration.

Example:

{
  "command": "python",
  "args": ["-m", "mcp_server_time", "--local-timezone=America/New_York"]
}

Example Interactions

  1. Get current time:
{
  "name": "get_current_time",
  "arguments": {
    "timezone": "Europe/Warsaw"
  }
}

Response:

{
  "timezone": "Europe/Warsaw",
  "datetime": "2024-01-01T13:00:00+01:00",
  "is_dst": false
}
  1. Convert time between timezones:
{
  "name": "convert_time",
  "arguments": {
    "source_timezone": "America/New_York",
    "time": "16:30",
    "target_timezone": "Asia/Tokyo"
  }
}

Response:

{
  "source": {
    "timezone": "America/New_York",
    "datetime": "2024-01-01T12:30:00-05:00",
    "is_dst": false
  },
  "target": {
    "timezone": "Asia/Tokyo",
    "datetime": "2024-01-01T12:30:00+09:00",
    "is_dst": false
  },
  "time_difference": "+13.0h",
}

Debugging

You can use the MCP inspector to debug the server. For uvx installations:

npx @modelcontextprotocol/inspector uvx mcp-server-time

Or if you've installed the package in a specific directory or are developing on it:

cd path/to/servers/src/time
npx @modelcontextprotocol/inspector uv run mcp-server-time

Examples of Questions for Claude

  1. "What time is it now?" (will use system timezone)
  2. "What time is it in Tokyo?"
  3. "When it's 4 PM in New York, what time is it in London?"
  4. "Convert 9:30 AM Tokyo time to New York time"

Development

Run the tests from src/time. They live in tests/: test_protocol.py drives the server through an MCP ClientSession in-process, test_entrypoints.py covers main(), python -m mcp_server_time and the console script, and test_server.py unit-tests the time helpers.

cd src/time
uv run pytest

Coverage is a separate command. It measures line and branch coverage of src/mcp_server_time, prints the missing lines, and writes coverage.json (ignored by git):

cd src/time
uv run --frozen pytest --cov --cov-report=term-missing --cov-report=json

Every file must reach 90% of its lines and 90% of its branches. Code that cannot be reached is marked # pragma: no cover # <reason>, always with the reason, rather than lowering the bar.

Build

Docker build:

cd src/time
docker build -t mcp/time .

Contributing

We encourage contributions to help improve mcp-server-time. Bug reports, ideas for new time-related tools, enhancements to existing functionality, and documentation improvements are all valuable.

For examples of other MCP servers and implementation patterns, see: https://github.com/modelcontextprotocol/servers

Contributions arrive as issues, not pull requests: the repository maintainers do the implementation. Open an issue with the bug report or feature request form, and if you have already prototyped a change, share the prompt you used rather than a diff. See CONTRIBUTING.md for the full policy.

License

mcp-server-time is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Metadata

Release files for mcp-server-time 2026.10.10

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-server-time 2026.10.10
File Size Uploaded
mcp_server_time-2026.10.10.tar.gz 83.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-server-time 2026.10.10
File Interpreter ABI Platform
mcp_server_time-2026.10.10-py3-none-any.whl Python 3 none any Details

Total release size: 92.2 kB

Release files / mcp_server_time-2026.10.10.tar.gz

Download URL mcp_server_time-2026.10.10.tar.gz
Size 83.7 kB
Tags Source
SHA-256 checksum
How to use checksums
cf51f9abd0f9b071acbd9de70d50e2ca33976fc5749fe8041ea7944d104f4256
BLAKE2b-256 checksum
How to use checksums
e3b4fdf80a05297afb4053b5c5dc94dd4d165a034e2fc68a54953c2f40f1872c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / mcp_server_time-2026.10.10-py3-none-any.whl

Download URL mcp_server_time-2026.10.10-py3-none-any.whl
Size 8.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
32983d5193af219359ccdac46c558bed75f9c930360e7437cc040a73984cc17c
BLAKE2b-256 checksum
How to use checksums
a2eda4fed01271866397abcb8ca76f0f47a76e63122142ac177b99cc78e4e53b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2026.10.10 This release

2 release files

0.6.2

2 release files

0.6.1

2 release files

0.6.0

1 release file

0.5.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page