temporal-mcp-server
Time, timezone and duration tools — IANA zones, conversion, DST-correct date arithmetic.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"temporal-mcp-server": {
"command": "npx",
"args": [
"temporal-mcp-server"
]
}
}
}Runnable packages
0.2.3stdioRemote endpoints
https://time.somamcp.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (5)
⚪info
Returns identity and build information for this server (name, version, build commit, runtime, capability counts)
Input Schema
{
"type": "object"
}🟢get_current_time(timezone)
Return the current time as an epoch, a UTC ISO-8601 timestamp, and the wall-clock time in a given timezone.
Input Schema
{
"type": "object",
"properties": {
"timezone": {
"description": "IANA timezone identifier, e.g. 'America/New_York'. Defaults to UTC.",
"type": "string"
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}⚪convert_timezone(isoTimestamp, sourceTimezone, targetTimezone)
Render an ISO-8601 timestamp as wall-clock time in a target timezone.
Input Schema
{
"type": "object",
"properties": {
"isoTimestamp": {
"type": "string",
"description": "ISO-8601 timestamp to convert, e.g. '2026-08-17T14:30:00Z'."
},
"sourceTimezone": {
"description": "IANA timezone used to interpret `isoTimestamp` when it carries no 'Z' or offset. Ignored otherwise. Defaults to UTC.",
"type": "string"
},
"targetTimezone": {
"type": "string",
"description": "IANA timezone identifier to render in."
}
},
"required": [
"isoTimestamp",
"targetTimezone"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}🟡add_duration(duration, isoTimestamp, timezone)
Add an ISO-8601 duration to a timestamp, in a timezone. Date units (Y/M/D) are calendar-aware: P1D across a DST boundary keeps the same wall-clock time the next day, and P1M on Jan 31 clamps to the end of February. Time units (H/M/S) are exact elapsed time, so PT24H really is 24 hours. Prefix the duration with '-' to subtract.
Input Schema
{
"type": "object",
"properties": {
"duration": {
"type": "string",
"description": "ISO-8601 duration, e.g. 'P1D', 'PT30M', 'P1Y2M3DT4H5M6S', or '-P1W'."
},
"isoTimestamp": {
"type": "string",
"description": "ISO-8601 timestamp to shift."
},
"timezone": {
"description": "IANA timezone governing the arithmetic — calendar units are applied to this zone's wall clock, and a timestamp with no 'Z' or offset is read as wall-clock time here. Defaults to UTC.",
"type": "string"
}
},
"required": [
"duration",
"isoTimestamp"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}⚪time_between(from, timezone, to)
Exact elapsed time between two ISO-8601 timestamps, broken into days/hours/minutes/seconds plus a human-readable summary. All components share one sign, so they sum correctly; `direction` is 'past', 'future', or 'same'.
Input Schema
{
"type": "object",
"properties": {
"from": {
"type": "string",
"description": "Start of the interval, as an ISO-8601 timestamp."
},
"timezone": {
"description": "IANA timezone used to interpret timestamps that carry no 'Z' or offset. Defaults to UTC.",
"type": "string"
},
"to": {
"type": "string",
"description": "End of the interval, as an ISO-8601 timestamp."
}
},
"required": [
"from",
"to"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}Community
Evidence