- Home
- MCP servers
- MCP Time Server
MCP Time Server
- python
0
GitHub Stars
python
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"siberianwm-mcp-time-server": {
"command": ".venv/bin/python",
"args": [
"server.py"
]
}
}
}This minimal MCP server serves the current time to clients. It is designed to be lightweight and lets clients decide the timezone, making it easy to integrate time data into various workflows and dashboards.
How to use
You connect to the time service from an MCP client and receive a stream or updates of the current time. The server expects a token for access and a specific path that the client should reach. Use the SOCKS/HTTP bridge or a direct MCP URL depending on your setup. In practice, you configure your MCP client with the server URL, include your authorization header, and set the client-side timezone so the time shown aligns with your locale.
Typical usage patterns include connecting via an HTTP-based MCP transport or a local/stdio setup. For HTTP transports, point the client at the remote server URL and provide the Authorization header with your token. For local stdio usage, you run the server locally and connect to the local endpoint as configured by your client.
How to install
Prerequisites: Python 3.13, a shell environment, and access to install dependencies.
python3.13 -m venv .venv
.venv/bin/pip install -r requirements.txt
Create the configuration file that the server loads on start. The file defines your access token, the port, and the path used by clients to reach the service.
{
"token": "your-secret-token",
"port": 23386,
"path": "/your-random-path"
}
Start the server using the Python interpreter from your virtual environment.
.venv/bin/python server.py
Configuration and notes
The server exposes a secure endpoint that clients access with the provided token. Use the path you configured to reach the service. If you run behind a reverse proxy or gateway, ensure the proxy forwards the path correctly and preserves the Authorization header.
Security and client tips
Keep your token secret and rotate it periodically. Use HTTPS whenever possible to protect the Authorization header in transit. When testing locally, you can use a secured tunneling method or a trusted certificate if your client enforces TLS.
Troubleshooting
If clients cannot connect, verify that the server is running and listening on the expected port. Check that the token in your client configuration matches the one stored in config.json. Confirm that the path configured on the server matches the path used by the client.
Available tools
getCurrentTime
Returns the current server time to the client; the timezone is determined by the client configuration.