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')
- Required arguments:
-
convert_time- Convert time between timezones.- Required arguments:
source_timezone(string): Source IANA timezone nametime(string): Time in 24-hour format (HH:MM)target_timezone(string): Target IANA timezone name
- Required arguments:
Installation
Using uv (recommended)
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...
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
mcpkey is needed when using themcp.jsonfile.
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
- Go to the Zencoder menu (...)
- From the dropdown menu, select
Agent Tools - Click on the
Add Custom MCP - Add the name and server configuration from below, and make sure to hit the
Installbutton
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
- 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
}
- 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
- "What time is it now?" (will use system timezone)
- "What time is it in Tokyo?"
- "When it's 4 PM in New York, what time is it in London?"
- "Convert 9:30 AM Tokyo time to New York time"
Build
Docker build:
cd src/time
docker build -t mcp/time .
Contributing
We encourage contributions to help expand and improve mcp-server-time. Whether you want to add new time-related tools, enhance existing functionality, or improve documentation, your input is valuable.
For examples of other MCP servers and implementation patterns, see: https://github.com/modelcontextprotocol/servers
Pull requests are welcome! Feel free to contribute new ideas, bug fixes, or enhancements to make mcp-server-time even more powerful and useful.
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.
Release files for mcp-server-time 2026.8.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_server_time-2026.8.18.tar.gz | 63.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_time-2026.8.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.1 kB
Release files / mcp_server_time-2026.8.18.tar.gz
| Download URL | mcp_server_time-2026.8.18.tar.gz |
|---|---|
| Size | 63.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec1313feb558a848838217d922bd218e9f7ca217cb0f7b890ee75ab94bf962e0
|
|
BLAKE2b-256 checksum How to use checksums |
321a5687ea89a5cb79f641141a7c010ff9c425bdf4e6cac02e8cfb49aa81f310
|
| 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 Aug 18, 2026.
Transparency logRelease files / mcp_server_time-2026.8.18-py3-none-any.whl
| Download URL | mcp_server_time-2026.8.18-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1407583af42dc0163909d855c9ef20114a12b4981c3975033721a7906cdd212a
|
|
BLAKE2b-256 checksum How to use checksums |
add9fcc7f85f0cdcfa8da9c650439128dd72be21855a126b745f17cf43f24b11
|
| 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 Aug 18, 2026.
Transparency log