mcp-time -node

This MCP Time Server Node provides a versatile set of time-related operations designed for LLM integration via the Model Context Protocol (MCP). It supports timezone conversions, current time retrieval in any IANA timezone, date arithmetic (adding or subtracting time), duration calculations, business day computations, business hours calculations, recurring event scheduling, flexible time formatting, and days-until queries. Tools are exposed as individual MCP actions such as get_current_time, convert_timezone, add_time, subtract_time, calculate_duration, get_business_days, next_occurrence, format_time, calculate_business_hours, and days_until. You can invoke these tools by sending MCP-like JSON-RPC requests to dist/index.js in a wired environment (e.g., Claude Code or Claude Desktop integration) or by running the server locally and issuing requests to the exposed methods. The server emphasizes high performance with caching and rate limiting, making it suitable for interactive chat assistants that require fast, repeated time calculations with robust validation.

Prerequisites:

• Node.js (14+ recommended) and npm
• git

Install from npm (recommended if published):

1. Install globally npm install -g mcp-time-server-node

2. Run the server (example using npx would also work if published): mcp-time-server-node

Local development / building from source:

1. Clone the repository git clone https://github.com/pshempel/mcp-time-node.git cd mcp-time-server-node

2. Install dependencies and build make setup # Install dependencies and build

3. Run tests (optional) make test

4. Run the server directly from the built artifact (example) node dist/index.js

Claude integration examples (may vary by environment):

• For Claude Code, add the server with the local path to the built index.js as shown in the README: claude mcp add tim-server /path/to/mcp-time-server-node/dist/index.js

Prerequisites summary:

• Node.js and npm installed
• Access to a terminal with Git
• (Optional) build tools if cloning from source and building locally

Tips and notes:

• If you deploy behind a gateway, ensure the port configuration and CORS (if applicable) are correctly set for MCP JSON-RPC requests.
• The server supports environment-driven configuration; tune RATE_LIMIT, RATE_LIMIT_WINDOW, CACHE_SIZE, and DEFAULT_TIMEZONE to match your workload.
• For testing, you can exercise the built-in tools with sample JSON-RPC payloads such as {'jsonrpc':'2.0','method':'tools/get_current_time','params':{'timezone':'UTC','format':'yyyy-MM-dd HH:mm:ss'}}.
• When using in Claude environments, prefer the provided Claude Code or Claude Desktop integration paths and ensure the correct command/args are set in your config.
• If you encounter INVALID_TIMEZONE or INVALID_DATE_FORMAT errors, verify that the input values conform to IANA timezones and ISO 8601 formats respectively.
• Build artifacts reside in dist/ after make build; ensure dist/index.js exists before starting the server.