Time MCP Server

Created By
koch3092a year ago
Overview

What is Time MCP Server?

Time MCP Server is a Model Context Protocol server that provides time and timezone conversion capabilities, enabling LLMs to access current time information and perform timezone conversions using IANA timezone names with automatic system timezone detection.

How to use Time MCP Server?

To use Time MCP Server, you can either run it using uv, install it via pip, or configure it for specific applications like Claude or Zed. After installation, you can interact with the server using JSON formatted requests to get current time or convert time between different timezones.

Key features of Time MCP Server?

  • Get current time in a specific timezone or system timezone.
  • Convert time between different timezones.
  • Automatic detection of system timezone.
  • Customizable configuration options for different environments.

Use cases of Time MCP Server?

  1. Retrieve the current time in various timezones.
  2. Convert scheduled meeting times across different timezones.
  3. Integrate with applications that require accurate time and timezone data.

FAQ from Time MCP Server?

  • Can Time MCP Server handle all IANA timezone names?

Yes! It supports all IANA timezone names for accurate conversions.

  • Is there a recommended way to install Time MCP Server?

Yes, using uv is recommended for ease of use, but it can also be installed via pip.

  • How can I customize the server's timezone detection?

You can override the automatic detection by specifying the --local-timezone argument in the configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
koch3092
Star
0
Language
Python
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