How do I use Time MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Time MCP Server what time is it in Tokyo right now?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Time MCP Server

by dumyCq

Overview Schema Source Related Servers Discussions Admin

Python

MCP Time Server

This is the MCP (Model Context Protocol) Time Server, extracted from the official modelcontextprotocol/servers repository.

Source

This server was originally located at:

Repository: https://github.com/modelcontextprotocol/servers
Path: /src/time
Original commit: Extracted from the main branch

Related MCP server: Time MCP Server

Description

A Model Context Protocol server that provides time and timezone functionality. This server enables LLMs to get current time information across different timezones.

Features

Get current time in any timezone
List available timezones
Convert times between timezones

Installation

# Using pip
pip install -e .

# Using uv
uv pip install -e .

Usage

The server can be used with any MCP-compatible client.

License

This project maintains the same license as the original modelcontextprotocol/servers repository.

Acknowledgments

All credit goes to the original authors at Anthropic and contributors to the modelcontextprotocol/servers project.

Available Tools

2 tools

convert_timeC

Convert time between timezones

ParametersJSON Schema

Name	Required	Description
`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.
`time`	Yes	Time to convert in 24-hour format (HH:MM)
`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 updatesAug 15, 2025
- First observedconvert_time
- First observedget_current_time

Deploy Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Scored 2026-04-18 08:55 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one converts time between timezones, while the other retrieves the current time in a specified timezone. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool based on the task.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (convert_time and get_current_time), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.

Tool Count2/5

With only two tools, the server feels thin for a time-related domain. While the tools cover basic operations, there are likely gaps such as scheduling, time arithmetic, or handling date formats that could enhance functionality. A count of 2 is borderline too few for a comprehensive time server.

Completeness2/5

The tool surface is significantly incomplete for a time server domain. It lacks essential operations like date manipulation, time arithmetic, scheduling, or handling recurring events. Agents may struggle with common time-related tasks beyond simple conversions and current time retrieval.

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
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
time-mcp A
io.github.jmavid
Current time, timezone conversion & date math for AI agents. On Cloudflare Workers.
Developer Tools
2
arjunkmrm-local02OAuth
ai.smithery
Get the current time in your chosen timezone and view common timezone information. Simplify schedu…
Location Services
2

Related MCP Servers

Time MCP Server
ampcome-mcps
A
license
B
quality
D
maintenance
Gives large language models time awareness capabilities through various time-related functions including current time retrieval, timezone conversion, and relative time calculations.
Updated a year ago (2025-07-14 05:21 UTC)
6
1,160
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
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 a year ago (2025-03-25 15:41 UTC)
2
2
MIT
Time MCP Server
Search
CarterPape
A
license
Not graded
quality
D
maintenance
Provides current time information and timezone conversion capabilities using IANA timezone names and automatic system detection. It enables LLMs to fetch current times across different regions and convert specific times between timezones.
Updated a year ago (2025-06-21 23:27 UTC)
MIT