Time Node MCP

What davidan90/time-node-mcp MCP server does

davidan90/time-node-mcp MCP server supplies date and time utilities through the Model Context Protocol. It is intended to reduce errors caused by timezone assumptions when an assistant answers questions about the current time, date, or day of the week.

The server supports IANA timezone identifiers such as America/New_York, Europe/London, and Asia/Tokyo. It can return the current time for a requested zone, convert a specified time from one zone to another, report the host system's timezone, and retrieve a date with day-of-week information. Daylight Saving Time transitions are handled as part of the timezone processing.

How it works

The MCP process accepts tool requests with timezone and date/time parameters, then returns structured JSON responses. Current-time requests require a timezone and can select an ISO, local, or full output format. Conversion requests specify source and destination zones, a 24-hour time, and optionally a calendar date. If no date is supplied for conversion, the current date is used.

The date utility takes an IANA timezone and can optionally include time details. A separate system-timezone operation requires no parameters and returns the machine's current timezone together with current time information. Invalid timezone names, malformed times, invalid dates, and system failures are reported with descriptive structured errors.

Setup and configuration

To run davidan90/time-node-mcp MCP server, use Node.js 18 or later with npm or yarn. Install the project dependencies, compile the TypeScript source, and then start the generated server. The documented development commands include npm install, npm run build, and npm start.

Claude Desktop can launch the built server as a local Node process. Its MCP configuration points the node command at the compiled dist/index.js file. The path must be changed to the actual installation location, and the project must be built before connecting. The README provides configuration locations for macOS and Windows.

For development, the project also documents watch mode, linting, and type checking through its npm scripts. No API key, hosted endpoint, or external service credential is described.

Tools and capabilities

The documented operations are:

• get_current_time: Gets the current date and time for an IANA timezone. Its optional format values are iso, local, and full.
• convert_time: Converts an HH:MM or HH:MM:SS value from a source timezone to a target timezone, optionally for a given YYYY-MM-DD date.
• get_system_timezone: Reports the system timezone and current time without input parameters.
• get_current_date: Returns the date and day of week for an IANA timezone, with an option to include time information.

These capabilities fit scheduling across regions, travel-related time checks, international team coordination, and questions about the current date in a particular location.

Limitations and notes

Requests depend on valid IANA timezone identifiers, including correct spelling and capitalization. The server uses the host system's current date and time as its base, so an incorrect system clock or system timezone can produce unexpected results. The provided material describes local execution after building the project; it does not document a published package, remote deployment, or support for clients beyond the Claude Desktop example.