Clockport

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Oct 29, 2026

Current time and timezone conversion for any IANA zone.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Clockport is a local MCP server that gives an assistant current time in any IANA timezone and converts a clock time between zones.

What you can do
  • Get the current time in a named IANA timezone, including wall-clock and ISO 8601 forms, weekday, UTC offset and DST status
  • Convert a time of day from a source timezone to a target timezone, returning the target date, ISO 8601 form and signed offset difference
  • Report unknown timezone names or malformed times as tool errors instead of guessing
  • Also usable as a command-line tool with plain-text or JSON output
When to use it
Useful when an assistant needs reliable local times or meeting-time conversions across zones, including daylight-saving differences, without relying on its own arithmetic.
Requirements
Runs as a local stdio process, started with npx from the npm package or from the container image via docker. No accounts, API keys, environment variables or headers are declared. Timezone data comes from the platform's IANA database through Node's Intl support.
Before you install
Conversions take only a time of day, so they use today's date in the source zone as the reference date; results around daylight-saving transitions reflect the offset in force today, and the reference date is returned with each result. The server is read-only and needs no credentials.

Installation

In SourceWeft

  1. Open Clockport in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

clockport

clockport tells you what time it is somewhere else, and what a given clock time in one place corresponds to in another. It answers two questions — "what time is it in Tokyo right now?" and "my call is at 12:00 New York time, what is that in London?" — from the command line or as an MCP server for agents.

All zone handling uses the IANA timezone database behind Node's Intl support, so daylight-saving changes are handled by the platform rather than by a fixed offset table.

Install

bash
npx @reneturcios/clockport now Europe/London

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/clockport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
# Current time in a zoneclockport now America/New_York# 2026-01-15 07:00:00 (America/New_York, 2026-01-15T07:00:00-05:00)
# Convert a time between zonesclockport convert America/New_York 12:00 Europe/London# 2026-10-26 12:00 America/New_York -> 2026-10-26 17:00 Europe/London (+5h)
# Machine-readable outputclockport now Asia/Tokyo --jsonclockport convert UTC 09:30 Asia/Kolkata --json
clockport --version

Exit codes: 0 on success, 1 when a zone or time cannot be handled (the error names the problem), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/clockport mcp

MCP client configuration:

json
{  "mcpServers": {    "clockport": {      "command": "npx",      "args": ["-y", "@reneturcios/clockport", "mcp"]    }  }}

Tools

ToolInputWhat it returns
get_current_timetimezone (string, required) — IANA timezone nameThe current time in that zone: wall-clock rendering, ISO 8601 form with offset, weekday, UTC offset in minutes, and whether DST is in effect.
convert_timesource_timezone (string, required), time (string, required, HH:MM 24-hour), target_timezone (string, required)The requested time rendered in the target zone, with the target date (which may differ from the source date), an ISO 8601 form, and the signed offset difference.

Unknown timezone names and times that are not valid HH:MM values are reported as tool errors rather than guessed at.

Reference date for conversions

convert_time takes a time of day but no date. Conversions therefore use today's date — the current calendar date in the source zone — as the reference date. This matters around daylight-saving transitions, where the offset difference between two zones can change from one week to the next; the result always reflects the difference in force today. The reference date used is included in every conversion result.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit 0903cf2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts