Time MCP Server
# 🚀 Time MCP Server: Giving LLMs Time Awareness Capabilities
[](https://smithery.ai/server/@yokingma/time-mcp) <a href="https://github.com/yokingma/time-mcp/stargazers"><img src="https://img.shields.io/github/stars/yokingma/time-mcp" alt="Github Stars"></a> <a href="https://github.com/yokingma/time-mcp/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-purple" alt="License"></a> <a href="https://github.com/yokingma/time-mcp/issues/new"><img src="https://img.shields.io/badge/Report a bug-Github-%231F80C0" alt="Report a bug"></a>
A Model Context Protocol (MCP) server implementation that allows LLMs to have time awareness capabilities.
<div align="center">
<img src="./assets/cursor.png"></img>
</div>
## Tools
- `current_time`: Get current time (UTC and local time)
- `relative_time`: Get relative time
- `get_timestamp`: Get timestamp for the time
- `days_in_month`: Get days in month
- `convert_time`: Convert time between timezones
- `get_week_year`: Get week and isoWeek of the year
## Installation
### Installing via Smithery
To install time-mcp for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@yokingma/time-mcp):
```bash
npx -y @smithery/cli install @yokingma/time-mcp --client claude
```
### Manually install (Optional)
```shell
npm install -g time-mcp
```
### using npx
```shell
npx -y time-mcp
```
## Running on Cursor
Your `mcp.json` file will look like this:
```json
{
"mcpServers": {
"time-mcp": {
"command": "npx",
"args": ["-y", "time-mcp"]
}
}
}
```
## Running on Windsurf
Add this to your `./codeium/windsurf/model_config.json` file:
```json
{
"mcpServers": {
"time-mcp": {
"command": "npx",
"args": ["-y", "time-mcp"]
}
}
}
```
## License
MIT License - see [LICENSE](./LICENSE) file for details.
TDQS
Scored across 6 tools
Most tools have distinct purposes, such as time conversion, current time retrieval, and timestamp generation. However, 'get_week_year' and 'relative_time' could be slightly ambiguous in scope, as both relate to temporal positioning, but their descriptions clarify the differences well.
The tools follow a consistent verb_noun pattern (e.g., convert_time, current_time) with clear, descriptive names. There are minor deviations like 'days_in_month' using plural form, but overall, the naming is highly readable and predictable.
With 6 tools, the server is well-scoped for time-related operations, covering core functionalities like conversion, current time, and date calculations. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset covers basic time operations but has notable gaps, such as missing date arithmetic (e.g., add/subtract days), time formatting, or scheduling tasks. While agents can work around this for simple queries, more complex time manipulations are not supported.