Simple Time MCP CLI

by Jaesun23

Simple Time MCP CLI provides simple time-related functionalities as an MCP (Model Context Protocol) server. This version operates in a one-time CLI mode, eliminating the need to run a separate server.

View on GitHub

Last updated: N/A

What is Simple Time MCP CLI?

Simple Time MCP CLI is a Model Context Protocol server that offers time-related functionalities through a command-line interface. It allows users to retrieve current time information, format dates, calculate date differences, add or subtract time from dates, and convert between timezones.

How to use Simple Time MCP CLI?

Install the CLI globally using npm: npm install -g Jaesun23/simple-time-mcp-cli. Configure Claude or Cursor by adding the MCP server configuration to their respective settings files, specifying the command and arguments. Use the CLI directly in the terminal or ask time-related questions within Claude/Cursor.

Key features of Simple Time MCP CLI

Current time retrieval in various timezones
Date/time formatting with customizable formats
Date difference calculation
Date addition/subtraction
Timezone conversion and information

Use cases of Simple Time MCP CLI

Getting the current time in a specific timezone
Calculating the difference between two dates
Converting a time from one timezone to another
Asking Claude/Cursor time-related questions like 'What time is it in Tokyo?'

FAQ from Simple Time MCP CLI

How do I install the Simple Time MCP CLI?

You can install it globally using npm: npm install -g Jaesun23/simple-time-mcp-cli.

How do I configure this for Claude or Cursor?

Add the MCP server configuration to their respective settings files, specifying the command as simple-time-mcp-cli and arguments as ['--mcp'].

Can I specify a timezone?

Yes, you can use the --timezone or --tz option followed by the desired timezone (e.g., --timezone "Asia/Seoul").

Can I change the date or time format?

Yes, you can use the --format option for time format (12h/24h) and --date-format to change the date representation.

What do I do if I get a 'command not found' error?

Verify that the global installation path (obtained from npm list -g --depth=0) is included in your system's PATH environment variable.