Time MCP server via HTTP
A Model Context Protocol (MCP) server providing time-related tools with dual-mode support:
This server allows LLMs to access various date/time functions through multiple connection methods.
MCP Central Server Card: https://guide-gen.mcpcentral.io/servers/io-github-mcpcentral-io-mcp-time
Provides the following MCP tools:
current_time: Get the current date and time in specified formats and timezones.relative_time: Get a human-readable relative time string (e.g., "in 5 minutes", "2 hours ago").days_in_month: Get the number of days in a specific month.get_timestamp: Get the Unix timestamp (milliseconds) for a given time.convert_time: Convert a time between different IANA timezones.get_week_year: Get the week number and ISO week number for a given date.mcp-time/
├── src/
│ └── index.ts # Cloudflare Worker entry point & MCP logic
├── package.json # Project dependencies and scripts
├── tsconfig.json # TypeScript configuration
└── wrangler.toml # Cloudflare Worker configuration
Install the package globally or use with npx:
# Global installation
npm install -g @mcpcentral/mcp-time
# Or use directly with npx
npx @mcpcentral/mcp-time
Connect directly to the deployed Cloudflare Worker:
Example:
https://mcp.time.mcpcentral.io
Configure your MCP client (e.g., Claude Desktop) to use the stdio transport:
{
"mcpServers": {
"time-server": {
"command": "npx",
"args": ["@mcpcentral/mcp-time"]
}
}
}
Or with global installation:
{
"mcpServers": {
"time-server": {
"command": "/path/to/node/bin/mcp-time"
}
}
}
Configure your MCP client to use the remote HTTP endpoint:
{
"mcpServers": {
"time-server": {
"url": "https://mcp.time.mcpcentral.io",
"transport": "streamable-http"
}
}
}
Clone the Repository:
git clone https://github.com/mcpcentral-io/mcp-time.git
cd mcp-time
Install Dependencies:
npm install
Build: Compile the TypeScript code:
npm run build
(This compiles src/index.ts to dist/index.js)
Test Locally:
Test Stdio Mode:
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | node dist/index.js
Test HTTP Mode (via Wrangler):
npx wrangler dev
This will start the server on http://localhost:8787. You can then test with curl or point your MCP client to this local endpoint.
Configure Cloudflare:
cp wrangler.toml.example wrangler.toml
Edit wrangler.toml to configure your domain (optional).
Login and Deploy:
wrangler login
npx wrangler deploy
Build the package:
npm run build
Publish:
npm publish --access public
NEW: Major providers have adopted the Model Context Protocol and now support Streamable HTTP servers directly. Anthropic, OpenAI, and Microsoft have all adopted this modern transport protocol.
📋 Protocol Note: Streamable HTTP is the modern replacement for the deprecated HTTP+SSE transport.
Anthropic's MCP Connector allows you to use Streamable HTTP servers directly through the Messages API without needing a separate MCP client.
The MCP Connector is perfect for this server since it uses the Streamable HTTP architecture. Simply include the server in your API requests:
curl https://api.anthropic.com/v1/messages \
-H "Content-Type: application/json" \
-H "X-API-Key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "anthropic-beta: mcp-client-2025-04-04" \
-d '{
"model": "claude-sonnet-4-20250514",
"max_tokens": 1000,
"messages": [{
"role": "user",
"content": "What time is it in Tokyo?"
}],
"mcp_servers": [{
"type": "url",
"url": "https://your.worker.url.workers.dev",
"name": "http-time-server"
}]
}'
OpenAI also supports Streamable HTTP servers through their Agents SDK using the MCPServerStreamableHttp class:
from agents.mcp.server import MCPServerStreamableHttp
# Connect to this Streamable HTTP server
server = MCPServerStreamableHttp({
"url": "https://your.worker.url.workers.dev",
"headers": {"Authorization": "Bearer your-token"}, # if needed
})
# Use the server in your OpenAI agent
await server.connect()
tools = await server.list_tools()
result = await server.call_tool("current_time", {"timezone": "Asia/Tokyo"})
Microsoft Copilot Studio now supports Streamable HTTP servers with MCP integration generally available. You can connect this server to Copilot Studio by:
Keep an eye out as more MCP clients adopt support for Streamable HTTP. Here are a few resources that maintain lists of MCP clients and their capabilities:
Test your server using these web-based inspection tools:
The official MCP Inspector is also available:
npx @modelcontextprotocol/inspectorStart your server:
# Local HTTP server
npx wrangler dev
# Or use deployed URL: https://mcp.time.mcpcentral.io
Connect with an inspector:
http://localhost:8787 or https://mcp.time.mcpcentral.ioTest the stdio transport directly:
# Test initialization
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | npx @mcpcentral/mcp-time
# Test tool call
echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"current_time","arguments":{"timezone":"America/New_York"}}}' | npx @mcpcentral/mcp-time
The inspector will show all six time-related tools:
current_time: Test with different timezones (e.g., "America/New_York", "Europe/London")relative_time: Test with various time strings (e.g., "2024-12-25T00:00:00Z")days_in_month: Test with different months and yearsget_timestamp: Convert date-time strings to Unix timestampsconvert_time: Convert between different timezonesget_week_year: Get week numbers for specific datesTry these test cases in the inspector:
// current_time
{"timezone": "Asia/Tokyo", "format": "iso"}
// relative_time
{"time": "2024-12-25T00:00:00Z"}
// days_in_month
{"month": 2, "year": 2024}
// get_timestamp
{"time": "2024-06-15T12:00:00Z"}
// convert_time
{"time": "2024-06-15T12:00:00", "from": "UTC", "to": "America/Los_Angeles"}
// get_week_year
{"date": "2024-06-15"}
Use the inspector to verify:
The MCP Inspector provides the most comprehensive way to test your server before integrating it with AI clients.
⚠️ IMPORTANT: This example server has NO authentication or security measures implemented.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @mcpcentral/mcp-timeMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-mcpcentral-io-mcp-time": {
"command": "npx",
"args": [
"-y",
"@mcpcentral/mcp-time"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.mcpcentral-io/mcp-time works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.