The point is not the tool but where it lives: the setup the README leads with is the global Cursor config, so every project gets a real UTC reading without another server entry. Three formats cover the usual needs — a timestamp for logs, ISO for records, plain datetime for prose.
A small MCP server that returns the current UTC time. It exists so an assistant working in an editor can read a real clock — ISO 8601, a human-readable datetime, or a Unix timestamp — instead of inferring the date from context.
- The current UTC time in a chosen format — `get_current_time_utc`
- Three `format` values: `iso` (the default, `2025-01-15T10:30:45Z`), `datetime` (`2025-01-15 10:30:45`) and `timestamp` (`1736939445`)
- A global Cursor setup — `~/.cursor/mcp.json` on macOS and Linux — so the server is present in every project rather than per-repository
Python 3.8 or higher and `pip install -e .`. The server runs as `python -m mcp_time_server.server` or through the installed `mcp-time-server` script, and the Cursor entry sets `cwd` and `PYTHONPATH` to the checkout's `src` directory. Nothing to authorize. The project is `mcp-time-server` 0.1.0.
Build from source — clone the repository and build it, then point your client at the binary