mcp-datetime
Click on "Install 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-datetimeShow me the current time 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: 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 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. Dates show when Glama detected each change.
1 tool update
v0.1.4- First observed
get_datetime
TDQS
Only one tool exists, so there is no possibility of confusion or overlap.
With a single tool, naming is trivially consistent and follows a clear verb_noun pattern.
A single tool for a datetime server feels too thin; users would expect additional utilities like timezone conversion or formatting.
The server only provides current datetime in various formats. Missing common operations such as date parsing, arithmetic, or timezone handling.
Maintenance
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
Get the current time in your preferred timezone or any region you specify. Browse concise informatβ¦
Current time by timezone, astronomy events, and moon phases
Current time in any IANA time zone, plus the full time-zone list. Via timeapi.io.
Related MCP Servers
- AlicenseCqualityDmaintenanceProvides 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.215MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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.73MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools to get the current date and time in various formats (ISO, Unix timestamp, human-readable, custom) with configurable timezone support.MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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.903MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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