MCPTimeServer

Created By
mekanixmsa year ago
Overview

what is MCPTimeServer?

MCPTimeServer is a Model Context Protocol (MCP) server that provides accurate current time from internet time servers with support for custom timezones.

how to use MCPTimeServer?

To use MCPTimeServer, install the required dependencies, configure your preferred timezone, and run the server in Claude Desktop. You can then use the get_current_time tool to fetch the current time in your configured timezone.

key features of MCPTimeServer?

  • Fetches accurate time from NTP servers (pool.ntp.org)
  • Supports custom timezone configuration via environment variable
  • Graceful error handling for network issues and invalid timezones
  • Compatible with Claude Desktop

use cases of MCPTimeServer?

  1. Fetching the current time for applications that require accurate timekeeping.
  2. Supporting multiple timezones for global applications.
  3. Integrating with other services that rely on accurate time data.

FAQ from MCPTimeServer?

  • Can MCPTimeServer handle multiple timezones?

Yes! You can configure any valid timezone from the IANA Time Zone Database.

  • What happens if the NTP server is unreachable?

The server gracefully handles network issues and falls back to UTC if the timezone is invalid.

  • Is MCPTimeServer easy to install?

Yes! Installation is straightforward with pip and requires minimal configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mekanixms
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago