English Français العربية

io.github.CloudCorpRecords/clockport

Registre officiel Cartes, voyage et météo

Current time and timezone conversion for any IANA zone.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @reneturcios/clockport
Claude Code 
claude mcp add clockport -- npx -y @reneturcios/clockport@0.1.0 mcp
Configuration JSON (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
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "clockport": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/cloudcorprecords/clockport:0.1.0",
                "mcp"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  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.

Questions fréquentes

Qu'est-ce que io.github.CloudCorpRecords/clockport ?

Current time and timezone conversion for any IANA zone.

Comment installer io.github.CloudCorpRecords/clockport ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add clockport -- npx -y @reneturcios/clockport@0.1.0 mcp. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.CloudCorpRecords/clockport ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.CloudCorpRecords/clockport est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.CloudCorpRecords/clockport ?

Il est publié par CloudCorpRecords. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.