mcp-datetime
mcp-日期时间
English |日语
一个日期时间格式化服务,作为 Claude 桌面应用程序的 MCP 服务器实现。支持生成各种格式的日期时间字符串。
注意:此软件包仅在 macOS 上测试过。Windows 兼容性尚未验证。
先决条件
在使用 mcp-datetime 之前,请确保已安装以下工具:
Python 3.12 或更高版本
uv(Python 包安装程序)
uvx(Python 包运行器)
Related MCP server: DateTime MCP Server
特征
✨ 支持各种日期时间格式
🇯🇵 日语支持
📁 优化文件名生成格式
🌏 准确的时区处理
🔧 与 Claude 桌面应用程序无缝集成
MCP 服务器组件
工具
服务器实现了一个工具:
get_datetime:以各种格式获取当前日期和时间将“格式”作为必需的字符串参数
根据指定格式返回格式化的日期时间字符串
支持多种格式类型,包括标准、日语和 ISO 格式
与 Claude 桌面应用程序一起使用
将以下内容添加到您的配置文件中:
配置文件位置(macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-datetime": {
"command": "uvx",
"args": ["mcp-datetime"]
}
}
}关于安装
如果您需要直接安装软件包(例如,用于开发或源代码检查),您可以使用以下方法之一:
从 PyPI 安装
pip install mcp-datetime从 GitHub 源安装
git clone https://github.com/ZeparHyfar/mcp-datetime.git cd mcp-datetime pip install -e .手动安装的示例
claude_desktop_config.json{ "mcpServers": { "mcp-datetime": { "command": "python", "args": ["-m", "mcp_datetime"], "env": { "PYTHON": "/path/to/your/python" } } } }将“/path/to/your/python”替换为你的实际 Python 解释器路径
例如,“/usr/local/bin/python3”或“/Users/username/.pyenv/versions/3.12.0/bin/python3”
基本示例
命令格式
# 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 桌面应用程序提示示例
用户
Please tell me the current time in date_slash format克劳德
I'll get the current date in date_slash format. The current date is 2024/12/12
支持的格式
格式名称 | 例子 | 描述 |
日期 | 2024年12月10日 | 标准日期格式 |
日期斜线 | 2024年12月10日 | 带斜线的日期 |
date_jp | 2024年12月10日 | 日语日期格式 |
日期时间 | 2024年12月10日 00:54:01 | 标准日期时间 |
datetime_jp | 2024年12月10日 00时54分01秒 | 日语日期时间 |
datetime_t | 2024年12月10日00:54:01 | 带有 T 分隔符的日期时间 |
袖珍的 | 20241210005401 | 紧凑的身份证格式 |
compact_date | 2024年12月10日 | 仅限紧凑日期 |
紧凑时间 | 005401 | 仅限紧凑时间 |
文件名_md | 20241210005401.md | Markdown 文件名 |
文件名_txt | 20241210005401.txt | 文本文件名 |
文件名_日志 | 20241210005401.日志 | 日志文件名 |
异质 | 2024年12月10日00:54:01+0900 | ISO 8601 格式 |
iso_basic | 20241210T005401+0900 | 基本 ISO 格式 |
日志 | 2024年12月10日 00:54:01.123456 | 以微秒为单位的日志格式 |
log_compact | 20241210_005401 | 紧凑日志格式 |
时间 | 00:54:01 | 仅限时间 |
time_jp | 00时54分01秒 | 日本时间格式 |
调试
由于 MCP 服务器通过 stdio 运行,调试起来可能比较困难。我们推荐使用MCP Inspector :
使用 PyPI 包
npx @modelcontextprotocol/inspector uvx mcp-datetime使用从 GitHub 下载的源代码
git clone https://github.com/ZeparHyfar/mcp-datetime.git npx @modelcontextprotocol/inspector uvx --directory ./mcp-datetime run mcp-datetime
执照
该项目根据 MIT 许可证获得许可 - 有关详细信息,请参阅LICENSE文件。
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.
MCP server for time in cities around the world, time zones, DST, conversion, and meetings.
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.115 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