Skip to main content
Glama
siberianwm

MCP Time Server

by siberianwm

MCP Time Server

Minimal MCP server that returns current time. Timezone configured on client side.

Installation

python3.13 -m venv .venv .venv/bin/pip install -r requirements.txt

Configuration

Create config.json:

{ "token": "your-secret-token", "port": 23386, "path": "/your-random-path" }

Running

.venv/bin/python server.py

Client Configuration

Claude Code CLI

claude mcp add time --transport sse \ --url "https://DOMAIN/PATH/sse" \ --header "Authorization: Bearer TOKEN" \ --header "X-Timezone: Asia/Novokuznetsk"

Claude Desktop

{ "mcpServers": { "time": { "command": "%APPDATA%\\npm\\mcp-remote.cmd", "args": [ "https://DOMAIN/PATH/sse", "--header", "Authorization:Bearer ${MCP_TIME_TOKEN}", "--header", "X-Timezone:${MCP_TIME_TIMEZONE}" ], "env": { "MCP_TIME_TOKEN": "your-token", "MCP_TIME_TIMEZONE": "Asia/Novokuznetsk" } } } }

Xray + Nginx Setup

When running behind Xray VLESS with ALPN-based fallbacks to nginx, add location block to nginx config (both h2 and http/1.1 server blocks):

location /PATH/ { proxy_pass http://127.0.0.1:PORT; proxy_http_version 1.1; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Connection ''; proxy_buffering off; proxy_cache off; proxy_read_timeout 86400s; send_timeout 86400s; chunked_transfer_encoding off; add_header X-Accel-Buffering no; }

Note: Xray path-based fallbacks only work with HTTP/1.1. For HTTP/2 (ALPN h2), requests go to nginx fallback, so nginx location is required.

-
security - not tested
F
license - not found
-
quality - not tested

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/siberianwm/mcp-time-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server