Skip to content
MCP server

America/Kentucky/Louisville clock

Returns the current local time for Louisville, Kentucky over a remote MCP endpoint

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

About America/Kentucky/Louisville clock

America/Kentucky/Louisville clock is an MCP server for time utilities. It runs as a hosted remote server, so there is nothing to install locally.

Louisville sits in the America/Kentucky/Louisville zone, so software that needs the local clock there has to account for its daylight-saving rules. This server answers that one question: it reports the current local time for that zone to an MCP client.

It is published as a remote streamable-http endpoint in the official MCP registry, so clients connect by URL rather than installing a package. The repository it comes from is a collection of small single-purpose MCP servers, each with its own endpoint and registry name.

It suits agent builders and automation that need a timezone-aware timestamp for one fixed location and want a standard MCP tool for it.

Install

Run in a terminal

claude mcp add --transport http tz-america-kentucky-louisville https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp

Add to Settings → Connectors → Add custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "tz-america-kentucky-louisville": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "tz-america-kentucky-louisville": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "tz-america-kentucky-louisville": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp

Enter a Name (for example "America/Kentucky/Louisville clock"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "tz-america-kentucky-louisville": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

What it does

Current local time
Reports the present time in the America/Kentucky/Louisville timezone.
Remote streamable-http endpoint
Reachable by URL over the streamable-http transport without a local install.
Registry listed
Published under an official MCP registry name with a single remote entry.

Good for

  • Give an AI assistant the current time in Louisville when scheduling or answering questions.
  • Add a timezone-aware clock reading to an agent workflow that serves Louisville users.
  • Test an MCP client's handling of a remote streamable-http tool with a simple time lookup.

America/Kentucky/Louisville clock FAQ

What timezone does this server report?

It reports the current local time for America/Kentucky/Louisville.

How is it connected?

The registry entry lists a single remote streamable-http endpoint, so no local package is required.

How do I add America/Kentucky/Louisville clock to Claude Code?

Run this command in your terminal: claude mcp add --transport http tz-america-kentucky-louisville https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/tz-america-kentucky-louisville/mcp

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers