get_current_timeLABSCO SUMMARY
Two tools, and a real HTTP story.
The time tools themselves are the ordinary pair, done properly: IANA zones, optional arguments with sensible defaults, and both the source and target zone echoed in the answer. What sets it apart is the HTTP mode — an origin allowlist that starts empty, wildcard subdomains supported, and * rejected outright once auth is on.
What it is
A small Go MCP server for time. It answers what time it is in a given timezone and converts a time from one zone to another, using the IANA time zone database, so the model reads a clock instead of guessing.
What you get
- The current time in a named timezone, or the system timezone when none is given —
get_current_time - A time converted between two zones, with an optional
timein 24-hourHH:MMform and a defaulted source zone —convert_time - Any IANA zone as an argument:
Europe/Warsaw,America/New_York,Asia/Tokyo,Australia/Sydney,Africa/Cairo - An HTTP transport alongside stdio —
go run . --transport=http— withGET /health,GET /capabilities, and MCP atTIME_HTTP_PATH(default/mcp)
Requirements
A Go toolchain: build with go build -o ./bin/mcp-time . and point the client at the binary. Nothing to authorize on the default stdio path. HTTP mode adds its own settings: TIME_HTTP_ADDRESS (default :8080), CORS off unless TIME_HTTP_CORS_ENABLED is set with an explicit TIME_HTTP_CORS_ORIGINS allowlist, and TIME_AUTH_ENABLED with a TIME_AUTH_SECRET_KEY of at least 32 characters when you want JWT on the endpoint.
Setup effort
Build from source — git clone https://github.com/chew-z/TimeMCP.git && cd TimeMCP
USE CASES
01
Letting a model answer "what time is it there"
Ask for the current time in a colleague's zone and get a clock reading rather than an inference from the conversation.
02
Scheduling across timezones
Convert a proposed meeting time from your zone into the other party's before writing the invitation.
03
Timestamping work in progress
Read the current time in the system timezone when a note, log line or draft needs a real time on it.
04
Serving several clients over HTTP
Run the HTTP transport with an explicit origin allowlist and a JWT secret instead of a per-client stdio process.
2 tools
Listed in project docs. Your client may show a different list.
convert_timeBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/chew-z/TimeMCP.git && cd TimeMCPBuild the binary first — the config block below points at its output path:
TERMINAL
go build -o ./bin/mcp-time .Add the mcpServers entry to claude_desktop_config.json; <YOUR_PATH_TO_BIN_MCP_TIME> is the absolute path of the binary you just built
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"time": {
"command": "<YOUR_PATH_TO_BIN_MCP_TIME>"
}
}
}
