English Français العربية

io.github.CloudCorpRecords/clockport

Official registry Maps, travel and weather

Current time and timezone conversion for any IANA zone.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @reneturcios/clockport
Claude Code 
claude mcp add clockport -- npx -y @reneturcios/clockport@0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "clockport": {
            "command": "npx",
            "args": [
                "-y",
                "@reneturcios/clockport@0.1.0",
                "mcp"
            ]
        }
    }
}
OCI package ghcr.io/cloudcorprecords/clockport:0.1.0
Claude Code 
claude mcp add clockport -- docker run -i --rm ghcr.io/cloudcorprecords/clockport:0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "clockport": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/cloudcorprecords/clockport:0.1.0",
                "mcp"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. clockport
  2. Install
  3. CLI
  4. MCP server
  5. Development
  6. License

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

npx @reneturcios/clockport now Europe/London

Or run the container image:

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

# Current time in a zone
clockport now America/New_York
# 2026-01-15 07:00:00 (America/New_York, 2026-01-15T07:00:00-05:00)

# Convert a time between zones
clockport 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 output
clockport now Asia/Tokyo --json
clockport 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:

npx -y @reneturcios/clockport mcp

MCP client configuration:

{
  "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

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

License

MIT — see LICENSE.

Frequently asked questions

What is io.github.CloudCorpRecords/clockport?

Current time and timezone conversion for any IANA zone.

How do I install io.github.CloudCorpRecords/clockport?

It runs on your machine. In Claude Code: claude mcp add clockport -- npx -y @reneturcios/clockport@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.CloudCorpRecords/clockport need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.CloudCorpRecords/clockport open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.CloudCorpRecords/clockport?

It is published by CloudCorpRecords. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.