Mcp_time_workdays_node

Created By
tanranv59 months ago
Overview

What is MCP Time & Workdays (Node)?

MCP Time & Workdays (Node) is a Node.js server based on the Model Context Protocol (MCP) that provides functionalities to retrieve the current time in a specified timezone and to obtain official workdays, holidays, and makeup workdays for a given year and month from multiple data sources.

How to use MCP Time & Workdays (Node)?

To use this project, you can either install it globally using npm or run it directly with npx. After installation, you can call the server to get the current time or workdays data.

Key features of MCP Time & Workdays (Node)?

  • Online data sources: Timor year aggregation API (default) and NateScarlet holiday-cn (as a free backup).
  • Unified output format for workdays, holidays, and makeup workdays.
  • Compatible with strict MCP clients, returning data in a text format.
  • Runs natively on Node.js 18+ without additional dependencies (except MCP SDK).

Use cases of MCP Time & Workdays (Node)?

  1. Retrieving the current time in different time zones.
  2. Getting official workdays and holidays for planning purposes.
  3. Integrating with other applications that require date and holiday information.

FAQ from MCP Time & Workdays (Node)?

  • What data sources does MCP Time & Workdays use?

It uses the Timor year aggregation API by default and supports NateScarlet holiday-cn as a backup.

  • Is there a need for an API key?

No, both data sources used are free and do not require an API key.

  • What is the output format?

The output is returned as a text type, which is a JSON string or plain text for better compatibility with MCP clients.

Server Config

{
  "mcpServers": {
    "time-and-workdays-node": {
      "command": "npx",
      "args": [
        "mcp-time-workdays-node"
      ],
      "env": {}
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
tanranv5
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