time-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_local_timeA | Return the current local date and time of the machine running this server. |
| get_time_in_timezoneA | Return the current date and time in the given IANA timezone (e.g. Asia/Tokyo, America/New_York). |
| list_timezonesA | Search available IANA timezone names. |
| get_time_from_ntpA | Get the current time from a public NTP server instead of the local clock.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: local clock time, timezone-specific time, timezone lookup, and NTP-sourced time. There is minor overlap between get_local_time and get_time_in_timezone when the timezone is omitted, but the descriptions make the intended differences clear.
Tool names follow a consistent get_/list_ verb pattern and clearly indicate their function. The naming style is uniform and predictable across all four tools.
Four tools is a well-scoped size for a time-focused MCP server. Each tool covers a distinct time-related need without unnecessary bloat.
The tool set covers the core time domain: local time, arbitrary timezone time, timezone discovery, and external NTP time. Timezone conversion and UTC access are achievable via get_time_in_timezone, so there are no obvious dead ends.