Timezone Helper
Give coding agents authoritative timezone lookups and conversions via TimezoneDB while you build scheduling, logging, or global-user features.
Overview
Timezone Helper is a MCP server for the Build phase that lets agents query TimezoneDB through regional streamable HTTP endpoints with an API key.
What is this MCP server?
- Streamable HTTP MCP remotes at https://tz-us.somdewan.com/mcp and https://tz-eu.somdewan.com/mcp with required region va
- Authenticates with X-TimezoneDB-Key (free key from https://timezonedb.com/register)
- Optional X-Backend-URL to point at https://api.timezonedb.com or a self-hosted mirror
- EU vs US endpoint choice for latency and data-region preference
- Ships as com.somdewan/timezone-helper version 5.0.0 on the MCP server schema
- Server version 5.0.0
- 2 regional MCP endpoint choices: us and eu
- Default upstream host https://api.timezonedb.com unless X-Backend-URL is set
What problem does it solve?
Builders and agents often infer UTC offsets incorrectly, which breaks scheduling, billing cutoffs, and user-visible clocks in global apps.
Who is it for?
Solo builders integrating global datetime behavior into an app while pair-programming with Claude Code or Cursor and wanting a small, keyed MCP integration.
Skip if: Projects that only need the browser Intl API for a single locale and never call an external timezone database.
What do I get? / Deliverables
After you register the remote MCP server with your TimezoneDB key and region, agents can rely on TimezoneDB-backed timezone operations instead of improvised offset math.
- Agent-callable TimezoneDB access over MCP
- Documented regional remote URL with secret API key header
- Optional custom TimezoneDB backend URL for mirrors or self-hosting
Recommended MCP Servers
Journey fit
Timezone resolution is wired when the product is built—agents call an external API during implementation—not as a one-off launch or growth tactic. This server is a remote HTTP bridge to TimezoneDB with API-key headers, which is classic third-party integration work in the build phase.
How it compares
TimezoneDB MCP integration, not a brainstorming or planning agent skill.
Common Questions / FAQ
Who is timezone-helper for?
Indie and solo developers who use MCP-enabled agents to build apps that must show or compute correct times across zones using TimezoneDB.
When should I use timezone-helper?
Use it during build when you need agent-accessible timezone lookups, conversions, or zone metadata instead of hard-coding offsets or fragile string guesses.
How do I add timezone-helper to my agent?
Add the streamable HTTP remote for your chosen region (us or eu), set the required X-TimezoneDB-Key header from timezonedb.com/register, and optionally set X-Backend-URL if you use a custom API host.