🔌

Time MCP

Utils450

Time and timezone conversion capabilities for AI agents.

Claude DesktopCursorWindsurf

Overview

Time and timezone conversion capabilities for AI agents.

Setup

Run with npx:

uvx mcp-server-time

Configuration

Added to claude_desktop_config.json

Documentation

Time MCP

Overview

Time MCP is a Model Context Protocol server that provides time and timezone conversion capabilities for AI agents. It enables agents to work with temporal data, handle timezone-aware operations, and perform accurate time calculations across different regions.

This server is essential for agents that need to:

  • Convert between timezones accurately
  • Work with relative time expressions ("in 2 hours", "next Monday")
  • Handle daylight saving time transitions
  • Schedule tasks at specific times
  • Display time in user's local timezone

Features

  • Timezone conversion: Convert between any IANA timezone
  • Relative time parsing: Understand natural language time expressions
  • Daylight saving awareness: Handle DST transitions correctly
  • Calendar integration: Work with dates, events, and schedules
  • Multiple format support: ISO 8601, Unix timestamps, human-readable

Installation

uvx mcp-server-time

Or via pip:

pip install mcp-server-time

Configuration

Add to your claude_desktop_config.json:

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

Available Tools

ToolDescription
get_current_timeGet the current time in a specified timezone
convert_timezoneConvert a time from one timezone to another
parse_relative_timeParse natural language time expressions
calculate_durationCalculate the duration between two times
list_timezonesList available IANA timezone names

Usage Examples

Example 1: Timezone Conversion

# Convert 3 PM New York time to Tokyo time
convert_timezone(
    time="15:00",
    from_tz="America/New_York",
    to_tz="Asia/Tokyo"
)
# Returns: "04:00 (next day)"

Example 2: Relative Time Parsing

# Parse "in 3 days at 2 PM"
parse_relative_time(
    expression="in 3 days at 2 PM",
    base_tz="America/Los_Angeles"
)
# Returns: ISO 8601 timestamp for the calculated time

Example 3: Scheduling

# Get current time in user's timezone
get_current_time(timezone="Europe/London")

# Calculate meeting duration
calculate_duration(
    start="2026-05-21T09:00:00Z",
    end="2026-05-21T10:30:00Z"
)
# Returns: "1 hour 30 minutes"

Pros

  • ✅ Accurate timezone handling with DST awareness
  • ✅ Natural language time expression parsing
  • ✅ Works with any IANA timezone
  • ✅ Lightweight and fast
  • ✅ Essential for global applications

Cons

  • ❌ Requires timezone knowledge for best results
  • ❌ Some edge cases with historical DST changes
  • ❌ Limited to time-related operations only

When to Use

  • Global scheduling: When working with users in multiple timezones
  • Event planning: When scheduling meetings or deadlines
  • Time-sensitive tasks: When accuracy matters (trading, logging)
  • Internationalization: When displaying time in user's local format
  • Calendar apps: When building scheduling or reminder features

Resources