Time MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Configures the listener host for the optional HTTP endpoint (used with `--transport streamable-http`). | |
| PORT | No | Configures the listener port for the optional HTTP endpoint (used with `--transport streamable-http`). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_timeA | Get current time in a specific timezone |
| convert_timeC | Convert time between timezones |
| get_time_agoB | Get the time a given number of days, hours, minutes and seconds ago in a specific timezone |
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 3 tools
Each tool has a clearly different output: current time, converted time, or an offset historical time. get_time_ago slightly overlaps with get_current_time (it's a parameterized variant) but the offset semantics are clear enough to avoid misselection.
All three names follow a clean verb_noun pattern (get_current_time, convert_time, get_time_ago) with consistent snake_case and time-related nouns.
Three tools is thin but defensible for a focused time utility. A couple more operations (e.g., time difference or formatting) could round it out without bloat.
Covers now, conversion, and past offsets, but there is no forward offset (future time), no difference/duration between two timestamps, and no formatting/parsing of arbitrary date strings, which are common agent needs.