Skip to main content
Glama
williamlang

Date-Time MCP Server

by williamlang

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 build

Usage

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 watch

License

MIT

Available Tools

1 tool
get_current_datetimeA

Returns the current date and time in ISO 8601 format

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.3/5.0
Behavior4/5

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.

Conciseness5/5

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.

Completeness5/5

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.

Parameters4/5

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.

Purpose5/5

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.

Usage Guidelines3/5

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. 1 tool updatev1.0.0
    • First observedget_current_datetime

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap. The tool's purpose is clear and distinct.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness2/5

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

ActivityStale
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

  • F
    license
    B
    quality
    D
    maintenance
    A 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
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides current local datetime information with timezone support. Serves as a minimal blueprint for building simple, single-purpose MCP servers.
    22
    1
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    A minimal MCP server that provides current time information with configurable timezone support set on the client side.
    -
  • 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
    -

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/williamlang/date-time-mcp'

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