All tools (except `get_local_time`) use accurate time from NTP servers. If NTP is unavailable, they gracefully fall back to local server time with a
MCP Simple Timeserver MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Simple Timeserver directly instead of describing what you should do. All tools (except get_local_time) use accurate time from NTP servers. If NTP is unavailable, they gracefully fall back to local server time with a notice.
Once MCP Simple Timeserver is connected, these are the calls the assistant has available:
get_local_time — Returns the current local time, day of week, and timezone from the user's machineget_utc — Returns accurate UTC time from an NTP time serverget_current_time — Returns current time with optional location, timezone, and calendar conversionscalculate_time_distance — Calculates duration between two dates/times (countdowns, elapsed time)get_holidays — Returns public holidays (and optionally school holidays) for a countryis_holiday — Checks if a specific date is a holiday in a given country or cityBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Simple Timeserver's toolset — get_local_time, get_utc, get_current_time and 3 more — is a fair guide to whether it matches your workflow. It is maintained by andybrandt; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_local_time | Returns the current local time, day of week, and timezone from the user's machine |
| get_utc | Returns accurate UTC time from an [NTP time server](https://en.wikipedia.org/wiki/Network_Time_Protocol) |
| get_current_time | Returns current time with optional location, timezone, and calendar conversions |
| calculate_time_distance | Calculates duration between two dates/times (countdowns, elapsed time) |
| get_holidays | Returns public holidays (and optionally school holidays) for a country |
| is_holiday | Checks if a specific date is a holiday in a given country or city |
{
"mcpServers": {
"simple-timeserver": {
"command": "npx",
"args": ["-y", "@smithery/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.