mcp-datetime
The mcp-datetime server provides datetime formatting services for the Claude Desktop Application, allowing you to get the current date and time in various formats.
Format options: Generate current date/time in standard, Japanese, ISO, compact, and filename-optimized formats (e.g.,
datetime,iso,compact,filename_md)Locale support: Includes Japanese-specific formats (e.g.,
date_jp,datetime_jp,time_jp)Timezone-aware: Handles accurate timezone information
Integration: Works seamlessly with the Claude Desktop App via the MCP protocol through a single
get_datetimetool
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-datetimewhat's the current date in Japanese format?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-datetime
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 formatsTakes "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-datetimeInstall from GitHub Source
git clone https://github.com/ZeparHyfar/mcp-datetime.git cd mcp-datetime pip install -e .Example
claude_desktop_config.jsonfor 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.mdClaude Desktop App prompt examples
User
Please tell me the current time in date_slash formatClaude
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-datetimeUsing 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 toolget_datetimeA
Get current date and time in various formats
| Name | Required | Description | Default |
|---|---|---|---|
| format | Yes | 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
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.
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.
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.
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.
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.
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.
1 tool update
- First observed
get_datetime
TDQS
Scored across 1 tool
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.
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.
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.
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
Related MCP Connectors
MCP server providing attendance data queries via the CloudTime API.
Read-only developer, date, finance, and text utilities. Authless remote MCP server by Clean.tools.
Timezone MCP โ wraps timeapi.io (free, no auth)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Claude Model Configuration Protocol (MCP) server that provides real-time timezone-aware date and time information.MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides tools to get the current date and time in various formats, supporting different timezones and custom formatting options.14 npm1MIT
- FlicenseAqualityDmaintenanceA 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-
- AlicenseAqualityDmaintenanceA 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.51MIT