Time & Location MCP Server
Provides containerization for the MCP server, allowing it to run in isolated environments with proper timezone and location data mounting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Time & Location MCP Server what time is it where I am?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Time & Location MCP Server
An MCP (Model Context Protocol) server that automatically detects and provides your current time and location information.
Features
Auto-detection: Automatically detects your system timezone and location
get_current_time: Returns current date/time in your local timezoneget_location: Returns your location based on IP geolocation
Related MCP server: whattimeisit-mcp
Setup & Running
Using Docker Compose
# Build and run (will auto-detect timezone and location)
docker-compose up --build
# Run in background
docker-compose up -d
# Override location if needed
CITY="Seattle" PROVINCE="WA" COUNTRY="USA" docker-compose upManual Docker Build
# Build image
docker build -t time-mcp-server .
# Run with timezone mounting
docker run -it \
-v /etc/localtime:/etc/localtime:ro \
-v /etc/timezone:/etc/timezone:ro \
time-mcp-serverMCP Client Configuration
For Cursor
Open Cursor Settings (Cmd+, on Mac or Ctrl+, on Windows/Linux)
Search for "Model Context Protocol" or navigate to Features > Beta
Enable MCP if not already enabled
Add this configuration:
{
"mcpServers": {
"time-location": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-v", "/etc/localtime:/etc/localtime:ro",
"-v", "/etc/timezone:/etc/timezone:ro",
"time_mcp-time-mcp-server"
]
}
}
}For Zed
Open Zed settings (Cmd+, on Mac)
Add to your settings.json:
{
"assistant": {
"version": "2",
"provider": {
"name": "anthropic"
},
"mcp": {
"servers": {
"time-location": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-v", "/etc/localtime:/etc/localtime:ro",
"-v", "/etc/timezone:/etc/timezone:ro",
"time_mcp-time-mcp-server"
]
}
}
}
}
}Note: Make sure the Docker container is built first with docker-compose build
Tools Available
get_current_time
Automatically detects your system timezone
Returns current time with timezone info
Includes ISO format, Unix timestamp, and UTC offset
get_location
Uses IP-based geolocation (requires internet)
Falls back to environment variables if set
Returns city, province/state, country, and coordinates
Environment Variables (Optional)
Override auto-detection by setting these variables:
TZ: Timezone (e.g., "America/New_York")CITY: Your cityPROVINCE: Your province/stateCOUNTRY: Your countryLATITUDE: Latitude coordinateLONGITUDE: Longitude coordinate
Available Tools
2 toolsget_current_timeA
Get the current date and time in your local timezone
Inputs: no named parameters.
get_locationB
Get your current location based on IP geolocation or system settings
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one retrieves time information, while the other retrieves location information. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the need.
Both tools follow a consistent verb_noun naming pattern (get_current_time and get_location) using snake_case. This uniformity makes the tool set predictable and easy to understand at a glance.
With only two tools, the server feels thin for a combined 'Time & Location' domain. While each tool is clear, the scope suggests more operations could be included, such as timezone conversions or location-based services, making the current count insufficient for comprehensive coverage.
The tool set is severely incomplete for the stated 'Time & Location' domain. It lacks essential operations like converting timezones, setting alarms, getting weather based on location, or calculating distances, leaving significant gaps that could cause agent failures in broader tasks.
Related MCP Connectors
MCP server for time in cities around the world, time zones, DST, conversion, and meetings.
MCP server providing attendance data queries via the CloudTime API.
An MCP server that automatically collects feedback on your MCP server.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that allows checking local time on the client machine or current UTC time from an NTP server2124 PyPI33MIT
- AlicenseBqualityDmaintenanceA lightweight mcp server that tells you exactly what time is it based on your IP.19MIT
- AlicenseAqualityDmaintenanceA MCP server that provides timezone-aware date and time operations. This server addresses the common issue where AI assistants provide incorrect date information due to timezone confusion.45MIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that provides current time information with configurable timezone support set on the client side.-