get_current_timeLABSCO SUMMARY
A model does not know what time it is, and this is the smallest possible fix.
Two calls: the current time in a zone you name or the system's own, and a conversion between a source and a target zone. System timezone detection means “what time is it for me” works with no configuration at all.
What it is
A time and timezone server working from IANA timezone names, with the system's own timezone detected automatically.
What you get
- get_current_time — the current time in an IANA timezone you name, such as America/New_York or Europe/London, or in the system timezone
- convert_time — a time converted from a source IANA timezone to a target one
Requirements
uvx runs it without installing anything; pip installs it as a package instead. No account and no key.
Setup effort
One command — uvx pape-mcp-server-time
USE CASES
Working out when a meeting lands for the other person
Convert the proposed time into their zone before you send the invitation.
Pinning down what “tomorrow” means
Get the real current time first, so a relative date resolves against the clock rather than the model's guess.
Scheduling across a team in several countries
Take the current time in each zone, then convert a candidate slot into all of them.
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.
Requires
uvx on PATH
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
{
"mcpServers": {
"time": {
"command": "uvx",
"args": [
"pape-mcp-server-time"
]
}
}
}uvx
uvx pape-mcp-server-time