About time
time is a read-only MCP server that supplies current times, timezone conversions, and daylight saving transition data. It is for assistants and agents that need live answers based on IANA timezone data, with source links included.
Key features
- 01Get current time for multiple places
- 02Convert times across time zones
- 03Look up time by coordinates
- 04Check daylight saving transitions
- 05Search cities in multiple languages
Use cases
- 01Compare current times in several cities
- 02Convert a meeting time between regions
- 03Find clock-change dates for a year
- 04Resolve a city name to its IANA timezone
MCP support
Exposes read-only time and city lookup tools through a public Streamable HTTP endpoint. It requires no API key, and responses include a source URL.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://worldclock.pro/mcpclaude mcp add --transport http pro-worldclock-time https://worldclock.pro/mcp{"mcpServers":{"pro-worldclock-time":{"type":"http","url":"https://worldclock.pro/mcp"}}}Open in Cursor{"servers":{"pro-worldclock-time":{"type":"http","url":"https://worldclock.pro/mcp"}}}Open in VS Code{"mcpServers":{"pro-worldclock-time":{"type":"http","url":"https://worldclock.pro/mcp"}}}{"mcpServers":{"pro-worldclock-time":{"serverUrl":"https://worldclock.pro/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
5| Parameter | Type | Required | Description |
|---|---|---|---|
| at | string | No | Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone). |
| locations | array | Yes |
Details
From the project READMEWorld Clock Pro MCP server
Give your AI agent a real clock. Public, read-only, no API key:
https://worldclock.pro/mcp
Models cannot reliably compute local times, DST transitions, or timezone math on their own. This server gives any MCP-capable assistant live answers from the IANA timezone database and a 224,000+ city registry, with the answer's source page cited in every response.
- Live endpoint:
https://worldclock.pro/mcp(Streamable HTTP, stateless, JSON-RPC 2.0) - How-to page: worldclock.pro/mcp
- Server card:
/.well-known/mcp/server-card.json - Registry name:
pro.worldclock/time(domain-verified)
Quick connect
Claude Code
claude mcp add --transport http worldclockpro-time https://worldclock.pro/mcp
Claude Desktop — Settings → Connectors → Add custom connector → paste the URL.
Cursor — paste into ~/.cursor/mcp.json (or use the button on worldclock.pro/mcp):
{ "mcpServers": { "worldclockpro-time": { "url": "https://worldclock.pro/mcp" } } }
VS Code
code --add-mcp '{"name":"worldclockpro-time","type":"http","url":"https://worldclock.pro/mcp"}'
ChatGPT — Settings → Apps & Connectors → Advanced settings → enable Developer mode → create a connector with the URL and No authentication. The server is read-only, so it works on plans where custom connectors are limited to read-only tools.
OpenClaw — add to openclaw.json:
{ "mcp": { "servers": { "worldclockpro-time": { "url": "https://worldclock.pro/mcp", "transport": "streamable-http" } } } }
MCP Inspector
npx @modelcontextprotocol/inspector
# Transport: "Streamable HTTP" → URL: https://worldclock.pro/mcp
Tools
| Tool | What it does | Try asking |
|---|---|---|
get_current_time | Current time in one or many places (up to 50 at once). | "What time is it in Tokyo, Paris, and UTC?" |
convert_time | Move one moment across time zones, DST-safe. | "If it's 9 AM Monday in New York, what time is it in Sydney?" |
time_by_coordinates | Time at any point on Earth, by latitude/longitude. | "What's the local time at 48.85, 2.35?" |
get_dst_transitions | DST observance and exact clock-change dates for any year. | "When do the clocks change in London this year?" |
search_cities | Multilingual city lookup → canonical slug, IANA zone, coordinates. | "Find cities called 'San Jose'." |
Every result includes a source_url linking the matching worldclock.pro page,
so answers can cite a live source.
Ways to describe a place
- City name or alias —
"Tokyo","new-york","nyc","Москва","São Paulo" - Timezone — IANA id (
"America/New_York") or abbreviation ("PST","ET","UTC") - Coordinates — latitude + longitude; the answer names the nearest city
Use as a Claude Code plugin
This repo is itself a plugin marketplace:
/plugin marketplace add worldclockpro/worldclock-mcp
/plugin install world-clock@worldclockpro
The plugin wires up the remote MCP server and installs the world-clock skill,
which teaches the assistant when to use which tool and the classic timezone traps
(EST vs ET, half-hour offsets, date-line weekday changes).
Use as an OpenClaw skill
The same skill follows the Agent Skills format:
npx clawhub@latest install world-clock # once published on ClawHub
# or copy skills/world-clock/ into your skills directory
Why trust it
- Read-only by design. Every tool declares
readOnlyHint: true. There are no write operations, no accounts, and nothing to sign in for. - No tracking. Queries are computed in memory and not stored. See the privacy policy.
- Live IANA data. DST rules come from the IANA timezone database, updated with the weekly data refresh, never hard-coded.
- Run by an established team. The people behind the World Clock Master (Apple Editor's Choice) and World Clock Pro apps.
- Domain-verified. The registry listing
pro.worldclock/timeis published with cryptographic proof of control of worldclock.pro.
Limits and errors
- Up to 50 locations per call (
search_citiesreturns up to 25 matches). - Per-IP rate limit: 60 calls per 10 seconds (HTTP 429 with
Retry-Afterbeyond that). - Invalid input returns structured errors (
LOCATION_NOT_FOUND,INVALID_TIMEZONE,AMBIGUOUS_INSTANT, ...) an agent can read and recover from.
Links
- Website: worldclock.pro
- Agent guide: worldclock.pro/llms.txt
- Support: [email protected]
MIT licensed. See SECURITY.md for the security posture.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.