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.
-
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:
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.
When using uv no specific installation is needed. We will
use uvx to directly run mcp-server-time.
uvx mcp-server-timeAlternatively you can install mcp-server-time via pip:
pip install mcp-server-timeAfter installation, you can run it as a script using:
python -m mcp_server_timeAdd 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"]
}
}
}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"]
}
},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"]
}
}
}
}- 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"]
}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"]
}- 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",
}You can use the MCP inspector to debug the server. For uvx installations:
npx @modelcontextprotocol/inspector uvx mcp-server-timeOr 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- "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"
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 pytestCoverage 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=jsonEvery 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.
Docker build:
cd src/time
docker build -t mcp/time .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.
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.