de en es ja ko ru zh

Time MCP Server

Name: Time MCP Server
Author: lchinglen

by lchinglen

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Time MCP Server

時刻とタイムゾーン変換機能を提供するModel Context Protocolサーバーです。このサーバーにより、LLMはIANAタイムゾーン名を使用して現在時刻の取得やタイムゾーン間の変換を実行でき、システムのタイムゾーンを自動検出します。

利用可能なツール

get_current_time - 特定のタイムゾーンまたはシステムのタイムゾーンで現在時刻を取得します。
- 必須引数:
  - timezone (string): IANAタイムゾーン名（例: 'America/New_York', 'Europe/London'）
convert_time - タイムゾーン間で時刻を変換します。
- 必須引数:
  - source_timezone (string): 元のIANAタイムゾーン名
  - time (string): 24時間形式の時刻 (HH:MM)
  - target_timezone (string): 変換先のIANAタイムゾーン名

インストール

uvを使用する（推奨）

uv を使用する場合、特別なインストールは不要です。uvx を使用して mcp-server-time を直接実行します。

uvx mcp-server-time

PIPを使用する

あるいは、mcp-server-time をpipでインストールすることもできます:

pip install mcp-server-time

インストール後、次のようにスクリプトとして実行できます:

python -m mcp_server_time

Related MCP server: Time MCP Server

設定

Claude.app向けの設定

Claudeの設定に追加します:

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

{
  "mcpServers": {
    "time": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "LOCAL_TIMEZONE", "mcp/time"]
    }
  }
}

{
  "mcpServers": {
    "time": {
      "command": "python",
      "args": ["-m", "mcp_server_time"]
    }
  }
}

Zed向けの設定

Zedのsettings.jsonに追加します:

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

"context_servers": {
  "mcp-server-time": {
    "command": "python",
    "args": ["-m", "mcp_server_time"]
  }
},

VS Code向けの設定

簡単なインストールには、以下のワンクリックインストールボタンのいずれかを使用してください...

Install with UV in VS Code Install with UV in VS Code Insiders

Install with Docker in VS Code

手動インストールの場合は、VS Codeのユーザー設定（JSON）ファイルに以下のJSONブロックを追加します。これを行うには、Ctrl + Shift + P を押して Preferences: Open User Settings (JSON) と入力します。

また、ワークスペース内の .vscode/mcp.json というファイルに追加することもできます。これにより、設定を他の人と共有できます。

mcp.json ファイルを使用する場合は、mcp キーが必要です。

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

{
  "mcp": {
    "servers": {
      "time": {
        "command": "docker",
        "args": ["run", "-i", "--rm", "mcp/time"]
      }
    }
  }
}

Zencoder向けの設定

Zencoderメニュー（...）に移動します。
ドロップダウンメニューから Agent Tools を選択します。
Add Custom MCP をクリックします。
以下の名前とサーバー設定を追加し、必ず Install ボタンを押してください。

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

カスタマイズ - システムタイムゾーン

デフォルトでは、サーバーはシステムのタイムゾーンを自動検出します。設定の args リストに --local-timezone 引数を追加すると、これを上書きできます。

例:

{
  "command": "python",
  "args": ["-m", "mcp_server_time", "--local-timezone=America/New_York"]
}

対話例

現在時刻を取得:

{
  "name": "get_current_time",
  "arguments": {
    "timezone": "Europe/Warsaw"
  }
}

応答:

{
  "timezone": "Europe/Warsaw",
  "datetime": "2024-01-01T13:00:00+01:00",
  "is_dst": false
}

タイムゾーン間で時刻を変換:

{
  "name": "convert_time",
  "arguments": {
    "source_timezone": "America/New_York",
    "time": "16:30",
    "target_timezone": "Asia/Tokyo"
  }
}

応答:

{
  "source": {
    "timezone": "America/New_York",
    "datetime": "2024-01-01T12:30:00-05:00",
    "is_dst": false
  },
  "target": {
    "timezone": "Asia/Tokyo",
    "datetime": "2024-01-01T12:30:00+09:00",
    "is_dst": false
  },
  "time_difference": "+13.0h",
}

デバッグ

MCPインスペクタを使用してサーバーをデバッグできます。uvxインストールの場合:

npx @modelcontextprotocol/inspector uvx mcp-server-time

または、パッケージを特定のディレクトリにインストールした場合や、それを開発している場合:

cd path/to/servers/src/time
npx @modelcontextprotocol/inspector uv run mcp-server-time

Claudeへの質問例

「今何時ですか？」（システムタイムゾーンが使用されます）
「東京の現在時刻は？」
「ニューヨークが午後4時のとき、ロンドンは何時ですか？」
「東京時間の午前9時30分をニューヨーク時間に変換してください」

ビルド

Dockerビルド:

cd src/time
docker build -t mcp/time .

貢献

mcp-server-time の拡張と改善に貢献することを歓迎します。新しい時刻関連ツールを追加したい場合、既存機能を強化したい場合、ドキュメントを改善したい場合など、あなたの貢献は貴重です。

他のMCPサーバーと実装パターンの例については、以下を参照してください: https://github.com/modelcontextprotocol/servers

プルリクエストを歓迎します！mcp-server-time をさらに強力で便利にするための新しいアイデア、バグ修正、機能拡張を自由に投稿してください。

ライセンス

mcp-server-time は MIT ライセンスの下でライセンスされています。つまり、MIT ライセンスの条件に従って、ソフトウェアを自由に使用、変更、配布できます。詳細については、プロジェクトリポジトリの LICENSE ファイルを参照してください。

Available Tools

2 tools

convert_timeC

Convert time between timezones

ParametersJSON Schema

Name	Required	Description
`time`	Yes	Time to convert in 24-hour format (HH:MM)
`source_timezone`	Yes	Source IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'Etc/UTC' as local timezone if no source timezone provided by the user.
`target_timezone`	Yes	Target IANA timezone name (e.g., 'Asia/Tokyo', 'America/San_Francisco'). Use 'Etc/UTC' as local timezone if no target timezone provided by the user.

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description carries full burden. It does not disclose any behavioral traits such as how time zones are handled, invalid inputs, or daylight saving time. The description is minimal and adds no transparency beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded. However, it could include more useful information without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description does not mention return format, error handling, or edge cases. For a time zone conversion tool, this is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 3 parameters. The description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Convert time between timezones', conveying the verb and resource. However, it does not differentiate from the sibling tool 'get_current_time', which might also involve time zones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. The description is a single phrase with no context about prerequisites or when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_current_timeC

Get current time in a specific timezones

ParametersJSON Schema

Name	Required	Description	Default
`timezone`	Yes	IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'Etc/UTC' as local timezone if no timezone provided by the user.

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only states 'Get current time' without disclosing output format, time source, or any behavioral details like handling of invalid timezones.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single sentence but grammatically flawed ('timezones'). It is concise but lacks clarity and proper structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description omits critical context such as return format, time source (server vs user), and error handling. Incomplete for a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides full description of the 'timezone' parameter with examples (100% coverage). The tool description adds no additional semantic value beyond what the schema offers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool gets current time in a specific timezone, but the grammar ('timezones') slightly reduces clarity. It distinguishes from sibling 'convert_time' by focusing on current time retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs the sibling 'convert_time' or any exclusion criteria. The description does not indicate context-specific usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesv1.0.3Sep 10, 2026
- First observedconvert_time
- First observedget_current_time

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored 2026-09-10 08:10 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves the current time for a given timezone, and the other converts a specified time between timezones. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tools follow the same verb_noun snake_case pattern: get_current_time and convert_time. The naming is predictable and clearly indicates the action and target.

Tool Count3/5

With only two tools, the server feels minimal for its domain, though both tools are essential and focused. The count is borderline but not unreasonable for a simple timezone utility.

Completeness4/5

The core time-related operations are covered: getting current time and converting between timezones. A list of supported timezones would be a minor useful addition, but agents can work reasonably well without it.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

time A
pro.worldclock
A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb.
Developer Tools
52
World Time A
com.invokera
Current time in any IANA time zone, plus the full time-zone list. Via timeapi.io.
Location Services
22
time-mcp A
io.github.jmavid
Current time, timezone conversion & date math for AI agents. On Cloudflare Workers.
Developer Tools
2
chrono-mcp A
io.github.nexus-api-lab
Deterministic time tools for AI agents: timezone conversion, business-day math, cron interpretation.
Developer Tools Calendar Management
2

Related MCP Servers

Time MCP Server
Developer Tools
dumyCq
A
license
B
quality
D
maintenance
Provides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.
Updated a year ago (2025-08-15 01:01 UTC)
2
MIT
Time MCP Server
asaficontact
A
license
B
quality
D
maintenance
Provides current time information and timezone conversion capabilities using IANA timezone names. Enables LLMs to get current time in any timezone and convert times between different timezones with automatic system timezone detection.
Updated a year ago (2025-10-02 02:44 UTC)
2
MIT
DateTime MCP Server
Developer Tools
pinkpixel-dev
A
license
A
quality
D
maintenance
Provides LLMs with current date and time information across any timezone, with configurable defaults and support for IANA timezone identifiers.
Updated 3 months ago (2026-07-13 01:41 UTC)
1
11 npm
3
Apache 2.0
Time MCP Server
Search
fisher1006
A
license
B
quality
D
maintenance
Provides current time information and timezone conversion capabilities using IANA timezone names with automatic system detection. It enables LLMs to fetch local or global times and convert specific timestamps between different regions.
Updated 2 years ago (2025-03-25 15:41 UTC)
2
2
MIT

Time MCP Server

利用可能なツール

インストール

uvを使用する（推奨）

PIPを使用する

設定

Claude.app向けの設定

Zed向けの設定

VS Code向けの設定

Zencoder向けの設定

カスタマイズ - システムタイムゾーン

対話例

デバッグ

Claudeへの質問例

ビルド

貢献

ライセンス

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Time MCP Server

Time MCP Server

DateTime MCP Server

Time MCP Server