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.

-

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

When usinguvno specific installation is needed. We will useuvxto directly runmcp-server-time.

{ "mcpServers": { "time": { "command": "uvx", "args": ["mcp-server-time"] } } }

{ "mcpServers": { "time": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/time"] } } }

{ "mcpServers": { "time": { "command": "python", "args": ["-m", "mcp_server_time"] } } }

"context_servers": [ "mcp-server-time": { "command": "uvx", "args": ["mcp-server-time"] } ],

"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 pressingCtrl + Shift + Pand typingPreferences: Open User Settings (JSON).

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

Note that themcpkey is needed when using themcp.jsonfile.

{ "mcp": { "servers": { "time": { "command": "uvx", "args": ["mcp-server-time"] } } } }

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

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

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

{ "name": "get_current_time", "arguments": { "timezone": "Europe/Warsaw" } }

{ "timezone": "Europe/Warsaw", "datetime": "2024-01-01T13:00:00+01:00", "is_dst": false }

{ "name": "convert_time", "arguments": { "source_timezone": "America/New_York", "time": "16:30", "target_timezone": "Asia/Tokyo" } }

{ "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-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

- "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"

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

Real-time stock heatmaps and investment tools delivered as interactive React components.