timezone-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEZONE_MCP_CONFIG | No | Path to a JSON configuration file with an 'always_timezones' array. This variable is overridden by TIMEZONE_MCP_ALWAYS_TIMEZONES if both are set. | |
| TIMEZONE_MCP_ALWAYS_TIMEZONES | No | Comma-separated list or JSON array of timezones to always include in output. JSON value '[]' disables default output zones. Empty value is rejected. |
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 |
|---|---|
| convert_timeA | Convert a timestamp from a source timezone. Returns configured default timezones plus any requested additional timezones, omitting the source timezone when it would duplicate the input. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and unambiguous.
The single tool name `convert_time` follows a clean verb_noun pattern, which is internally consistent.
The server offers just one tool, which feels thin for a general timezone utility. While the core conversion feature is present, users might expect additional operations like timezone listing or validation.
The conversion operation is fully covered, but the surface lacks an explicit way to list available timezones or configured defaults, which would be a minor gap for a timezone-focused MCP.