Skip to main content
Glama
DateTime MCP Server

DateTime MCP Server

by batteryshark

DateTime MCP Server

A simple MCP server that provides timezone-aware date and time information.

Tools

  • get_current_date(include_weekday=False) - Returns current date in ISO format (YYYY-MM-DD) with optional weekday

  • get_current_time() - Returns current time in configured format

Related MCP server: Date and Time MCP Server

Configuration

Set these environment variables (for stdio) or headers (for HTTP):

  • DEFAULT_TZ - Timezone identifier (e.g., "America/New_York", "Europe/London", "UTC")

  • TIMEFMT - Time format: "12" for 12-hour (2:30 PM) or "24" for 24-hour (14:30)

Fallbacks

  • Invalid timezone → defaults to UTC

  • TIMEFMT not "12" → defaults to 24-hour format

Usage Examples

STDIO (default)

{
  "date-time-mcp": {
    "command": "uv",
    "args": ["run", "python", "server.py"],
    "env": {
      "DEFAULT_TZ": "America/New_York",
      "TIMEFMT": "12"
    }
  }
}

HTTP Server

{
  "date-time-mcp": {
    "url": "http://localhost:8855",
    "headers": {
      "DEFAULT_TZ": "America/New_York",
      "TIMEFMT": "24"
    }
  }
}

Available Tools

2 tools
get_current_dateA

Get the current date in ISO format (YYYY-MM-DD).

Args: include_weekday: Whether to append the day of the week

Returns: ISO date string, optionally with weekday

Examples: get_current_date() -> "2024-01-15" get_current_date(include_weekday=True) -> "2024-01-15 (Monday)"

Inputs: include_weekday.

get_current_timeA

Get the current time in the configured format.

Returns: Time string in 12-hour or 24-hour format based on TIMEFMT setting

Examples: With TIMEFMT="12": "2:30 PM" With TIMEFMT="24": "14:30"

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_current_date retrieves date information, while get_current_time retrieves time information. There is no overlap in functionality, and an agent would easily differentiate between them based on their names and descriptions.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'get_current_' prefix, using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count2/5

    With only two tools, the server feels thin for a DateTime domain. A comprehensive DateTime server would typically include tools for date/time manipulation, formatting, timezone handling, or date arithmetic, not just current date and time retrieval.

    Completeness2/5

    The toolset is severely incomplete for a DateTime server. It lacks basic operations like date/time parsing, formatting control, timezone conversions, date arithmetic (add/subtract days), or comparisons. Agents will hit dead ends when needing anything beyond current date/time retrieval.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server providing timezone conversions and time-related operations via RESTful API endpoints, featuring comprehensive error handling and timezone database integration.
      -
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools to get the current date and time in various formats, supporting different timezones and custom formatting options.
      1
      15 npm
      1
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that automatically detects and provides current time and location information based on system timezone and IP geolocation.
      2
      -