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

Ein Model Context Protocol-Server, der Zeit- und Zeitzonenumrechnungsfunktionen bereitstellt. Dieser Server ermöglicht LLMs, aktuelle Zeitinformationen abzurufen und Zeitzonenumrechnungen mithilfe von IANA-Zeitzonennamen durchzuführen, mit automatischer Erkennung der Systemzeitzone.

Verfügbare Tools

get_current_time - Aktuelle Zeit in einer bestimmten Zeitzone oder der Systemzeitzone abrufen.
- Erforderliche Argumente:
  - timezone (string): IANA-Zeitzonenname (z. B. 'America/New_York', 'Europe/London')
convert_time - Zeit zwischen Zeitzonen umrechnen.
- Erforderliche Argumente:
  - source_timezone (string): Quell-IANA-Zeitzonenname
  - time (string): Zeit im 24-Stunden-Format (HH:MM)
  - target_timezone (string): Ziel-IANA-Zeitzonenname

Installation

Mit uv (empfohlen)

Bei Verwendung von uv ist keine spezielle Installation erforderlich. Wir werden uvx verwenden, um mcp-server-time direkt auszuführen.

uvx mcp-server-time

Mit PIP

Alternativ können Sie mcp-server-time über pip installieren:

pip install mcp-server-time

Nach der Installation können Sie es als Skript mit folgendem Befehl ausführen:

python -m mcp_server_time

Related MCP server: Time MCP Server

Konfiguration

Konfiguration für Claude.app

Fügen Sie zu Ihren Claude-Einstellungen hinzu:

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

Konfiguration für Zed

Fügen Sie zu Ihrer Zed settings.json hinzu:

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

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

Konfiguration für VS Code

Für eine schnelle Installation verwenden Sie einen der untenstehenden Ein-Klick-Installationsbuttons...

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

Install with Docker in VS Code

Für die manuelle Installation fügen Sie den folgenden JSON-Block zu Ihrer Datei „User Settings (JSON)“ in VS Code hinzu. Sie können dies tun, indem Sie Ctrl + Shift + P drücken und Preferences: Open User Settings (JSON) eingeben.

Optional können Sie ihn zu einer Datei namens .vscode/mcp.json in Ihrem Arbeitsbereich hinzufügen. Dadurch können Sie die Konfiguration mit anderen teilen.

Beachten Sie, dass der Schlüssel mcp erforderlich ist, wenn Sie die Datei mcp.json verwenden.

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

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

Konfiguration für Zencoder

Gehen Sie zum Zencoder-Menü (...)
Wählen Sie im Dropdown-Menü Agent Tools aus.
Klicken Sie auf Add Custom MCP.
Fügen Sie den Namen und die Serverkonfiguration von unten hinzu und stellen Sie sicher, dass Sie auf den Button Install klicken.

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

Anpassung - Systemzeitzone

Standardmäßig erkennt der Server automatisch die Zeitzone Ihres Systems. Sie können dies überschreiben, indem Sie das Argument --local-timezone zur args-Liste in der Konfiguration hinzufügen.

Beispiel:

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

Beispiel-Interaktionen

Aktuelle Zeit abrufen:

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

Antwort:

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

Zeit zwischen Zeitzonen umrechnen:

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

Antwort:

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

Debugging

Sie können den MCP-Inspektor verwenden, um den Server zu debuggen. Für uvx-Installationen:

npx @modelcontextprotocol/inspector uvx mcp-server-time

Oder wenn Sie das Paket in einem bestimmten Verzeichnis installiert haben oder daran entwickeln:

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

Beispiele für Fragen an Claude

„Wie spät ist es gerade?“ (wird die Systemzeitzone verwendet)
„Wie spät ist es in Tokio?“
„Wenn es in New York 16 Uhr ist, wie spät ist es in London?“
„Konvertieren Sie 9:30 Uhr Tokio-Zeit in New Yorker Zeit.“

Build

Docker-Build:

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

Mitwirken

Wir freuen uns über Beiträge, die helfen, mcp-server-time zu erweitern und zu verbessern. Ob Sie neue zeitbezogene Tools hinzufügen, bestehende Funktionen verbessern oder die Dokumentation verbessern möchten – Ihr Beitrag ist wertvoll.

Beispiele für andere MCP-Server und Implementierungsmuster finden Sie unter: https://github.com/modelcontextprotocol/servers

Pull Requests sind willkommen! Zögern Sie nicht, neue Ideen, Fehlerbehebungen oder Verbesserungen beizutragen, um mcp-server-time noch leistungsfähiger und nützlicher zu machen.

Lizenz

mcp-server-time ist unter der MIT-Lizenz lizenziert. Das bedeutet, dass Sie die Software frei verwenden, modifizieren und verbreiten können, vorbehaltlich der Bedingungen der MIT-Lizenz. Weitere Details finden Sie in der Datei LICENSE im Projekt-Repository.

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

Verfügbare Tools

Installation

Mit uv (empfohlen)

Mit PIP

Konfiguration

Konfiguration für Claude.app

Konfiguration für Zed

Konfiguration für VS Code

Konfiguration für Zencoder

Anpassung - Systemzeitzone

Beispiel-Interaktionen

Debugging

Beispiele für Fragen an Claude

Build

Mitwirken

Lizenz

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