Skip to main content
Glama
enesjakozh
ZeparHyfar

mcp-datetime

by ZeparHyfar
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

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: DateTime MCP 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_datetimeB

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

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool returns current date/time in various formats, which is basic behavioral information. However, it lacks details about whether this is a read-only operation, if it requires any permissions, how it handles timezones, or what happens on errors. For a tool with no annotation coverage, this is insufficient disclosure.

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, efficient sentence that communicates the core purpose without any unnecessary words. It's appropriately sized and front-loaded with the essential information.

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

Completeness3/5

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

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is reasonably complete for basic understanding. However, it lacks information about return values, error handling, and timezone behavior which would be helpful for a datetime tool.

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?

The description mentions 'various formats' which hints at the format parameter, but the input schema already provides 100% coverage with a comprehensive list of format options. The description adds minimal value beyond what's in the schema, so it meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('current date and time'), specifying the action and what it returns. It also mentions the key capability 'in various formats' which adds useful context. However, with no sibling tools to distinguish from, it cannot achieve the highest score for sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives or in what contexts it's appropriate. It simply states what the tool does without any usage instructions, prerequisites, or exclusions.

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 update
    • First observedget_datetime
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'get_datetime' has a clear and distinct purpose that cannot be mistaken for any other tool in this set.

Naming Consistency5/5

The naming pattern is trivially consistent as there is only one tool. The tool name 'get_datetime' follows a clear verb_noun convention, and with no other tools to compare against, it maintains perfect consistency within the set.

Tool Count2/5

A single tool for a datetime server is too minimal for the apparent scope. While 'get_datetime' provides current date and time, a datetime domain typically includes operations like formatting, parsing, timezone conversion, or date arithmetic, making this set feel incomplete and underpowered.

Completeness1/5

The tool surface is severely incomplete for a datetime server. It only offers getting the current datetime in various formats, lacking essential operations such as parsing strings to dates, converting timezones, calculating date differences, or manipulating dates (e.g., adding days). This will cause significant agent failures in datetime-related tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

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

  • Time MCP

    samay58
    A
    license
    Not graded
    quality
    D
    maintenance
    A Claude Model Configuration Protocol (MCP) server that provides real-time timezone-aware date and time information.
    MIT

  • DateTime MCP Server

    TakanariShimbo
    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
    29
    1
    MIT

  • Utility MCP Server

    Love-Gwen2025
    F
    license
    A
    quality
    D
    maintenance
    A general-purpose MCP server providing time-related utilities such as fetching current time, Unix timestamps, and formatting services. It supports both local stdio and remote SSE communication modes for versatile AI client integration.
    3
    -

  • mcp-datetimeday

    cfdude
    A
    license
    A
    quality
    D
    maintenance
    A lightweight MCP server providing comprehensive date, time, and day-of-week information. It supports relative time calculations, timezone conversions, and detailed calendar metadata like week numbers and quarters.
    5
    1
    MIT

Appeared in Searches

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/ZeparHyfar/mcp-datetime'

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