Date-Time MCP Server
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., "@Date-Time MCP ServerWhat is the current date and time?"
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.
Date-Time MCP Server
A simple Model Context Protocol (MCP) server that provides the current date and time.
Features
Returns current date and time in ISO 8601 format
Includes Unix timestamp
Provides timezone information
Returns human-readable formatted date/time
Related MCP server: MCP DateTime Server
Installation
npm install
npm run buildUsage
With Claude Desktop
Add this to your Claude Desktop configuration file:
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"date-time": {
"command": "node",
"args": ["/absolute/path/to/date-time-mcp/build/index.js"]
}
}
}Testing
You can test the server using the MCP Inspector or any MCP client.
Available Tools
get_current_datetime
Returns the current date and time information.
Parameters: None
Returns:
{
"datetime": "2025-12-08T16:57:00.000Z",
"timestamp": 1733676420000,
"timezone": "America/New_York",
"formatted": "12/8/2025, 11:57:00 AM"
}Development
# Build the project
npm run build
# Watch mode for development
npm run watchLicense
MIT
Available Tools
1 toolget_current_datetimeA
Returns the current date and time in ISO 8601 format
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosure. It states the return format (ISO 8601) and implies a read-only operation via 'returns'. It does not mention timezone specifics, but ISO 8601 typically includes offset information, reducing ambiguity.
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, concise sentence with no filler. It front-loads the main verb and resource, and every word adds value.
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 zero-parameter, output-only tool, the description fully explains what the agent will receive. No output schema is needed since the format is explicitly stated. The tool is simple enough that this is complete.
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?
The tool has zero parameters, and the schema correctly reflects this. The baseline for 0 params is 4, and the description adds no parameter information because none exists, which is appropriate.
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 returns the current date and time in ISO 8601 format. The verb 'returns' and the resource 'current datetime' are specific and unambiguous, making it self-explanatory even without sibling context.
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 explicit guidance on when to use is provided, but the tool is inherently simple with no alternatives or prerequisites. The usage is implied from the description, which is acceptable for such a straightforward getter.
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
v1.0.0- First observed
get_current_datetime
TDQS
With only one tool, there is no possibility of ambiguity or overlap. The tool's purpose is clear and distinct.
The single tool name 'get_current_datetime' follows a clear verb_noun pattern, is descriptive, and uses consistent snake_case. There are no other names to conflict with.
A single tool is on the low end of the spectrum. While it covers a basic need, a date-time server might reasonably include more tools (e.g., timezone conversion, formatting), so the count feels slightly thin.
The server only provides the current date/time, but a typical date-time utility would also handle conversions, formatting, or timezone lookups. This leaves significant gaps for common use cases.
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
Timezone MCP — wraps WorldTimeAPI (free, no auth)
A basic MCP server to operate on the Postman API.
Related MCP Servers
- FlicenseBqualityDmaintenanceA simple MCP server that provides accurate date and time information to Claude models, ensuring they always use the correct current date and time when creating time-sensitive content.3-
- AlicenseNot gradedqualityDmaintenanceProvides current local datetime information with timezone support. Serves as a minimal blueprint for building simple, single-purpose MCP servers.221MIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that provides current time information with configurable timezone support set on the client side.-
- 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-
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/williamlang/date-time-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server