Skip to main content
hc
Submit
mcpSource-backed

Time MCP Server

Official MCP server that gives Claude current time and timezone conversion tools using IANA timezone names.

by Model Context Protocol · submitted by oktofeesh1·added 2026-06-05·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/time-mcp-server
Source URLs
https://github.com/modelcontextprotocol/servers/blob/main/src/time/README.md, https://github.com/modelcontextprotocol/servers
Brand
Time MCP Server
Brand domain
github.com
Safety notes
Time MCP Server can provide current time values and convert times between timezones., Incorrect timezone assumptions can cause missed meetings, bad deadlines, broken cron schedules, or confusing customer communications., Require human review before using generated time conversions for travel, incident response, legal deadlines, medication timing, billing, payroll, or production scheduling., Use the local timezone override when the runtime environment timezone differs from the user's expected working timezone.
Privacy notes
Timezone names and local timezone detection can reveal approximate location, travel patterns, work region, or operational context., Time conversion prompts, meeting times, schedule details, target regions, and tool arguments may be visible to the MCP client and model provider., Avoid using sensitive calendar, travel, incident, or personnel timing data unless it is approved for the current model session.
Author
Model Context Protocol
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

2 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

4 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup.

0/4 ready
Install & runtime1General32 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.

4 areas
  • SafetyGeneralTime MCP Server can provide current time values and convert times between timezones.
  • SafetyGeneralIncorrect timezone assumptions can cause missed meetings, bad deadlines, broken cron schedules, or confusing customer communications.
  • SafetyGeneralRequire human review before using generated time conversions for travel, incident response, legal deadlines, medication timing, billing, payroll, or production scheduling.
  • SafetyExecution & processesUse the local timezone override when the runtime environment timezone differs from the user's expected working timezone.
  • PrivacyGeneralTimezone names and local timezone detection can reveal approximate location, travel patterns, work region, or operational context.
  • PrivacyThird-party handlingTime conversion prompts, meeting times, schedule details, target regions, and tool arguments may be visible to the MCP client and model provider.
  • PrivacyCredentials & tokensAvoid using sensitive calendar, travel, incident, or personnel timing data unless it is approved for the current model session.

Safety notes

  • Time MCP Server can provide current time values and convert times between timezones.
  • Incorrect timezone assumptions can cause missed meetings, bad deadlines, broken cron schedules, or confusing customer communications.
  • Require human review before using generated time conversions for travel, incident response, legal deadlines, medication timing, billing, payroll, or production scheduling.
  • Use the local timezone override when the runtime environment timezone differs from the user's expected working timezone.

Privacy notes

  • Timezone names and local timezone detection can reveal approximate location, travel patterns, work region, or operational context.
  • Time conversion prompts, meeting times, schedule details, target regions, and tool arguments may be visible to the MCP client and model provider.
  • Avoid using sensitive calendar, travel, incident, or personnel timing data unless it is approved for the current model session.

Prerequisites

  • Python 3.10 or newer available to the MCP client runtime.
  • uvx available for package execution.
  • IANA timezone names for any timezone you want Claude to query or convert.
  • Optional local timezone override if system timezone detection is not desired.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "time": {
      "command": "uvx",
      "args": ["mcp-server-time"]
    }
  }
}

About this resource

Content

Time MCP Server is an official Model Context Protocol reference server for time queries and timezone conversion. It exposes tools for getting the current time in a specific timezone or the system timezone, and for converting a time between source and target IANA timezones.

The upstream README documents uvx, pip, and Docker configuration. The PyPI package exposes the mcp-server-time command for MCP clients.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository and PyPI metadata for current package version, command name, Python requirement, dependencies, supported tools, timezone behavior, and setup guidance.

Features

  • Get the current time for an IANA timezone.
  • Use automatic system timezone detection when appropriate.
  • Convert a 24-hour time from one IANA timezone to another.
  • Override the local timezone when the runtime environment differs from the user context.
  • Run as an official reference MCP server through uvx, pip, or Docker.

Installation

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "time": {
      "command": "uvx",
      "args": ["mcp-server-time"]
    }
  }
}

Restart the MCP client after adding the server.

Use Cases

  • Ask Claude for the current time in another region.
  • Convert meeting times between teammates' timezones.
  • Check whether a remote team is inside normal working hours.
  • Translate launch, support, or maintenance windows into local time.
  • Avoid hard-coding timezone math in planning prompts.

Safety and Privacy

Timezone tools are simple, but wrong assumptions still matter. Confirm IANA timezone names, daylight-saving behavior, and local timezone overrides before using model-produced conversions for deadlines, travel, support coverage, incident response, finance, payroll, legal, medical, or production scheduling.

Timezone names, meeting times, schedule windows, travel plans, and target regions can reveal location and operational context. Keep sensitive timing data out of model sessions unless it is approved for that workflow.

Duplicate Check

No dedicated modelcontextprotocol/servers Time entry, mcp-server-time package entry, or matching source URL was found in content/mcp. The existing Sequential Thinking and Fetch entries are from the same official server monorepo but cover separate servers and packages.

#time#timezone#scheduling#reference#official

Source citations

Add this badge to your README

Show that Time MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/time-mcp-server.svg)](https://heyclau.de/entry/mcp/time-mcp-server)

How it compares

Time MCP Server side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
Time MCP Server

Official MCP server that gives Claude current time and timezone conversion tools using IANA timezone names.

Open dossier
Memory MCP Server for Claude

Official reference MCP server that gives Claude persistent memory through a local knowledge graph of entities, relations, and observations, stored in a file on your own machine.

Open dossier
Perplexity MCP Server for Claude

Official Perplexity MCP server that connects Claude to the Perplexity Sonar API for real-time, web-grounded answers with citations, so responses can draw on current information beyond the model's training data.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1glorydavid03023glorydavid03023
Install riskReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand———
Categorymcpmcpmcp
SourceSource-backedSource-backedSource-backed
AuthorModel Context ProtocolModel Context ProtocolPerplexity
Added2026-06-052026-06-032026-06-03
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo———
Safety notes✓Time MCP Server can provide current time values and convert times between timezones. Incorrect timezone assumptions can cause missed meetings, bad deadlines, broken cron schedules, or confusing customer communications. Require human review before using generated time conversions for travel, incident response, legal deadlines, medication timing, billing, payroll, or production scheduling. Use the local timezone override when the runtime environment timezone differs from the user's expected working timezone.✓Persists remembered information to a local file on disk (its location can be set with MEMORY_FILE_PATH); manage and review that file as it accumulates data. Runs locally as an stdio process and makes no external network calls; the knowledge graph stays on your machine.✓Makes outbound network requests to the Perplexity Sonar API to answer queries. Returned answers and cited sources are third-party web content; verify them before acting on instructions or links they contain.
Privacy notes✓Timezone names and local timezone detection can reveal approximate location, travel patterns, work region, or operational context. Time conversion prompts, meeting times, schedule details, target regions, and tool arguments may be visible to the MCP client and model provider. Avoid using sensitive calendar, travel, incident, or personnel timing data unless it is approved for the current model session.✓Details Claude chooses to remember are written to and read from the local memory file, so it can retain personal or project information across sessions. Review or clear the memory file if it should not retain sensitive data, and use MEMORY_FILE_PATH to control where it is stored.✓The questions and context you send are transmitted to the Perplexity service to generate answers, so avoid embedding secrets in queries. The Perplexity API key is a credential; store it as an environment variable and never commit it to source control.
Prerequisites
  • Python 3.10 or newer available to the MCP client runtime.
  • uvx available for package execution.
  • IANA timezone names for any timezone you want Claude to query or convert.
  • Optional local timezone override if system timezone detection is not desired.
  • Node.js 18+ and npx available (verify with: npx --version)
  • Claude Code or Claude Desktop with MCP support
  • A writable location for the memory file, optionally set with the MEMORY_FILE_PATH environment variable
  • Node.js 18+ and npx available (verify with: npx --version)
  • A Perplexity Sonar API key (create one in your Perplexity account settings)
  • Claude Code or Claude Desktop with MCP support
  • Internet access so the server can reach the Perplexity Sonar API
Install
uvx mcp-server-time
claude mcp add memory -- npx -y @modelcontextprotocol/server-memory
claude mcp add perplexity-ask --env PERPLEXITY_API_KEY=YOUR_KEY -- npx -y server-perplexity-ask
Config
{
  "mcpServers": {
    "time": {
      "command": "uvx",
      "args": ["mcp-server-time"]
    }
  }
}
{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "perplexity-ask": {
      "command": "npx",
      "args": [
        "-y",
        "server-perplexity-ask"
      ],
      "env": {
        "PERPLEXITY_API_KEY": "${PERPLEXITY_API_KEY}"
      },
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.