Pacific/Auckland clock
Remote MCP server that returns the current local time in Pacific/Auckland
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Pacific/Auckland clock
Pacific/Auckland clock is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This server does one narrow job: it reports the current local time for the Pacific/Auckland time zone (New Zealand). It is reachable as a remote streamable-http endpoint, so there is nothing to install; an MCP client just connects to the hosted URL.
It is one of a series of single-purpose utility servers published under the same GitHub repository, each registered under its own name in the MCP registry. The README describes the collection as public MCP servers aimed at autonomous clients, and also points to a separate set of promotional entries for an advertising service called Agent Ads, so the endpoint is hosted by a third party and not by a time-zone library vendor.
It suits agents and workflows that need a quick, fixed-zone clock lookup for New Zealand without handling time-zone conversion themselves. No tool names, parameters or response format are documented in the registry entry.
Install
Run in a terminal
claude mcp add --transport http tz-pacific-auckland https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"tz-pacific-auckland": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"tz-pacific-auckland": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tz-pacific-auckland": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"tz-pacific-auckland": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Auckland local time
- Returns the current local time for the Pacific/Auckland time zone.
- Remote streamable-http
- Served as a hosted streamable-http MCP endpoint, so no local package is needed.
- Single-purpose design
- Covers one fixed time zone, keeping the server simple for agents to call.
- Registry-listed
- Registered in the official MCP registry as io.github.sadri-dridi/tz-pacific-auckland.
Good for
- Let an agent check the current time in New Zealand before scheduling a message
- Show Auckland local time in an assistant answering questions about NZ business hours
- Validate time-zone-aware logic in an MCP client against a hosted clock
- Coordinate meetings with teams based in Auckland
Pacific/Auckland clock FAQ
What does this server do?
It returns the current local time in the Pacific/Auckland time zone.
How do I connect to it?
Use the streamable-http remote URL listed in the MCP registry entry; no package installation is required.
Is it part of a larger project?
Yes. It is one of several small utility servers in the named-mcp-utilities repository, each with its own registry name.
Does it cover other time zones?
This entry covers only Pacific/Auckland.
How do I add Pacific/Auckland clock to Claude Code?
Run this command in your terminal: claude mcp add --transport http tz-pacific-auckland https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-pacific-auckland/mcp
What are the best alternatives to Pacific/Auckland clock?
The closest alternatives to Pacific/Auckland clock are Pacific/Chatham clock, Pacific/Apia clock, Pacific/Tahiti clock, Pacific/Noumea clock and Pacific/Norfolk clock.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.