概要
What is IoEHub MCP Time Server?
A robust MCP (Model Context Protocol) Time Server that provides the current Unix timestamp in multiple formats, designed for AI models like Claude and Cursor that lack direct access to the current time.
How to use IoEHub MCP Time Server?
Install via npm (npm install) or clone the repository. Start using the Windows batch file (start-mcp-server.bat), direct Node.js command (node ioehub-time.js), or npm start. Configure it in your MCP client (Claude, Cursor) by adding a JSON entry pointing to the batch file or the script.
Key features of IoEHub MCP Time Server
- Provides current time in seven formats (Unix, human-readable, UTC, etc.)
- Extremely reliable; stays running even after stdin/stdout closures
- Self-healing – resists termination attempts
- Comprehensive logging to stderr and a timestamped log file
- Fully compliant with the Model Context Protocol
- Integrates seamlessly with Claude, Cursor, and other MCP clients
Use cases of IoEHub MCP Time Server
- AI assistants that need the current time for contextual responses
- Timestamp generation for AI-assisted coding in Cursor IDE
- Adding time awareness to any MCP‑compatible agent
FAQ from IoEHub MCP Time Server
What time formats does the server provide?
It returns unix_time, unix_ms, human_readable (ISO 8601), formatted (local), utc, date_only, and time_only.
Does the server actually shut down when asked?
No. The shutdown method is implemented gracefully, but the server intentionally stays running to maintain availability.
How do I integrate it with Claude or Cursor?
Add the server to your MCP configuration (mcpServers) with the path to start-mcp-server.bat (Windows) or ioehub-time.js (Unix/macOS). Claude and Cursor will automatically access time via MCP function calls.
Where are logs stored?
Logs are written to both stderr and to a file in the logs directory. Each instance creates a new timestamped log file.
What dependencies are required?
Node.js is required. Start commands assume Node.js is installed and available.
