MCP-timeserver
# MCP-timeserver
A simple MCP server that exposes datetime information to agentic systems and chat REPLs
<a href="https://glama.ai/mcp/servers/tth5eto5n7"><img width="380" height="200" src="https://glama.ai/mcp/servers/tth5eto5n7/badge" alt="MCP-timeserver MCP server" /></a>
## Components
### Resources
The server implements a simple datetime:// URI scheme for accessing the current date/time in a given timezone, for example:
```
datetime://Africa/Freetown/now
datetime://Europe/London/now
datetime://America/New_York/now
```
### Tools
The server exposes a tool to get the current local time in the system timezone:
```python
>>> get_current_time()
"The current time is 2024-12-18 19:59:36"
```
## Quickstart
### Install
use the following json
```json
{
"mcpServers": {
"MCP-timeserver": {
"command": "uvx",
"args": ["MCP-timeserver"]
}
}
}
```
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clear, so an agent cannot misselect between non-existent alternatives.
The single tool name follows a clear verb_noun pattern (get-current-time), and with no other tools to compare, there is no inconsistency. The naming is straightforward and predictable.
A single tool for a time server feels thin and under-scoped, as it only provides current time retrieval without obvious related operations like time conversion, formatting, or scheduling. This minimal set may limit functionality for typical time-related tasks.
The tool surface is severely incomplete for a time server domain, lacking basic operations such as converting between timezones, formatting times, or handling dates. It covers only a narrow slice of potential time-related functionality, likely causing agent failures in broader scenarios.