Skip to main content
Glama

Add to Cursor Add to VS Code Add to Claude Add to ChatGPT Add to Codex Add to Gemini

mcp-datetime

Python Version MCP Version License

English | ζ—₯本θͺž

A datetime formatting service implemented as an MCP server for the Claude Desktop Application. Supports generation of datetime strings in various formats.

Note: This package has been tested only on macOS. Windows compatibility has not been verified.

Prerequisites

Before using mcp-datetime, ensure you have the following tools installed:

  • Python 3.12 or later

  • uv (Python package installer)

  • uvx (Python package runner)

Related MCP server: MCP Time Server

Features

  • ✨ Support for various datetime formats

  • πŸ‡―πŸ‡΅ Japanese language support

  • πŸ“ Optimized formats for filename generation

  • 🌏 Accurate timezone handling

  • πŸ”§ Seamless integration with Claude Desktop App

MCP Server Components

Tools

The server implements one tool:

  • get_datetime: Get current date and time in various formats

    • Takes "format" as a required string argument

    • Returns formatted datetime string based on specified format

    • Supports multiple format types including standard, Japanese, and ISO formats

Usage with Claude Desktop App

Add the following to your config file:

Config file location (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json

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

About Installation

If you need to install the package directly (e.g., for development or source code inspection), you can use one of these methods:

  • Install from PyPI

    pip install mcp-datetime
  • Install from GitHub Source

    git clone https://github.com/ZeparHyfar/mcp-datetime.git
    cd mcp-datetime
    pip install -e .
  • Example claude_desktop_config.json for manual installation

    {
      "mcpServers": {
        "mcp-datetime": {
          "command": "python",
          "args": ["-m", "mcp_datetime"],
          "env": {
            "PYTHON": "/path/to/your/python"
          }
        }
      }
    }

    Replace "/path/to/your/python" with your actual Python interpreter path

    e.g., "/usr/local/bin/python3" or "/Users/username/.pyenv/versions/3.12.0/bin/python3"

Basic Examples

  • Command format

    # Standard datetime format
    call datetime-service.get_datetime {"format": "datetime"}
    # Result: 2024-12-10 00:54:01
    
    # Japanese format
    call datetime-service.get_datetime {"format": "datetime_jp"}
    # Result: 2024εΉ΄12月10ζ—₯ 00ζ™‚54εˆ†01η§’
    
    # Filename format
    call datetime-service.get_datetime {"format": "filename_md"}
    # Result: 20241210005401.md
  • Claude Desktop App prompt examples

    • User

      Please tell me the current time in date_slash format
    • Claude

      I'll get the current date in date_slash format.
      
      The current date is 2024/12/12

Supported Formats

Format Name

Example

Description

date

2024-12-10

Standard date format

date_slash

2024/12/10

Date with slashes

date_jp

2024εΉ΄12月10ζ—₯

Japanese date format

datetime

2024-12-10 00:54:01

Standard datetime

datetime_jp

2024εΉ΄12月10ζ—₯ 00ζ™‚54εˆ†01η§’

Japanese datetime

datetime_t

2024-12-10T00:54:01

DateTime with T separator

compact

20241210005401

Compact format for IDs

compact_date

20241210

Compact date only

compact_time

005401

Compact time only

filename_md

20241210005401.md

Markdown filename

filename_txt

20241210005401.txt

Text filename

filename_log

20241210005401.log

Log filename

iso

2024-12-10T00:54:01+0900

ISO 8601 format

iso_basic

20241210T005401+0900

Basic ISO format

log

2024-12-10 00:54:01.123456

Log format with microseconds

log_compact

20241210_005401

Compact log format

time

00:54:01

Time only

time_jp

00ζ™‚54εˆ†01η§’

Japanese time format

Debugging

Since MCP servers run over stdio, debugging can be challenging. We recommend using the MCP Inspector:

  • Using PyPI package

    npx @modelcontextprotocol/inspector uvx mcp-datetime
  • Using downloaded source code from GitHub

    git clone https://github.com/ZeparHyfar/mcp-datetime.git
    npx @modelcontextprotocol/inspector uvx --directory ./mcp-datetime run mcp-datetime

License

This project is licensed under the MIT License - see the LICENSE file for details.

Available Tools

1 tool
get_datetimeA

Get current date and time in various formats

ParametersJSON Schema
NameRequiredDescriptionDefault
formatYes Available formats: - date: 2024-12-10 - date_slash: 2024/12/10 - date_jp: 2024εΉ΄12月10ζ—₯ - datetime: 2024-12-10 00:54:01 - datetime_jp: 2024εΉ΄12月10ζ—₯ 00ζ™‚54εˆ†01η§’ - datetime_t: 2024-12-10T00:54:01 - compact: 20241210005401 - compact_date: 20241210 - compact_time: 005401 - filename_md: 20241210005401.md - filename_txt: 20241210005401.txt - filename_log: 20241210005401.log - iso: 2024-12-10T00:54:01+0900 - iso_basic: 20241210T005401+0900 - log: 2024-12-10 00:54:01.123456 - log_compact: 20241210_005401 - time: 00:54:01 - time_jp: 00ζ™‚54εˆ†01η§’

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description must carry the burden of behavioral disclosure. It implies a read-only operation but does not explicitly state that it has no side effects or that it returns the current server time. The description is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently communicates the tool's function without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one well-documented parameter and no output schema, the description covers the essential information. It is complete for its complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter, which already provides extensive detail on the 'format' options. The description adds no additional meaning beyond what the schema already conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action ('Get') and resource ('current date and time in various formats'), providing a specific and unambiguous purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. Since there are no sibling tools listed, this is a minor gap, but the description does not include any contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.4
    • First observedget_datetime

TDQS

A3.6/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or overlap.

Naming Consistency5/5

With a single tool, naming is trivially consistent and follows a clear verb_noun pattern.

Tool Count2/5

A single tool for a datetime server feels too thin; users would expect additional utilities like timezone conversion or formatting.

Completeness2/5

The server only provides current datetime in various formats. Missing common operations such as date parsing, arithmetic, or timezone handling.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    Provides current time and date information with timezone support and multiple formatting options. Enables AI assistants to answer time-related queries in different timezones with detailed temporal information.
    2
    15
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides time and date functionality with support for multiple formats and timezones, enabling users to get current time/date, format timestamps, and retrieve comprehensive datetime information.
    73
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides tools to get the current date and time in various formats (ISO, Unix timestamp, human-readable, custom) with configurable timezone support.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides current time and time difference calculations in ISO format (YYYY-MM-DD HH:mm:ss) using JavaScript Date. Supports both Windows and macOS for use with Claude desktop.
    90
    3
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fastmcp-me/mcp-datetime'

If you have feedback or need assistance with the MCP directory API, please join our Discord server