Server facts
time MCP Server
Project
- Author
- modelcontextprotocol
- Website
- modelcontextprotocol.io
- License
- Not specified
- Category
- Productivity
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- Not recordedPart of the modelcontextprotocol/servers monorepo
- Last commit
- Data as of
Tags
- mcp server
- time
- timezone
Overview
Regional clock queries and cross-timezone comparisons are handled through Time’s get_current_time and convert_time tools. The current-time tool retrieves a clock reading for an IANA timezone, while the server also supports the system’s local zone through automatic detection. For conversion, the caller supplies source and destination timezone names alongside a time expressed in 24-hour HH:MM format. These tools let an assistant answer questions about the current time in a city or translate a given local time into another region’s equivalent.
Local timezone detection can be overridden in the server configuration when a different default is needed. The documentation provides setup examples for Claude.app, Zed, VS Code, and Zencoder, with launch options covering uvx, a pip-installed Python package, and Docker. Communication uses stdio. For development and troubleshooting, the README describes using the MCP inspector, alongside instructions for building a Docker image. The project’s scope centers on clock information and timezone conversion rather than broader calendar workflows.
time setup notes
- time records stdio only; confirm a network transport upstream before planning remote access.
- time: Part of the modelcontextprotocol/servers monorepo
- time has no recorded license; confirm reuse terms in its repository.