Skip to main content
Glama
README.md
# @mcpx-digital/timezone

**MCP server for IANA timezone conversion, cross-zone “what time when”, and meeting overlap windows.**

Pure **date-fns-tz / Intl** — no external time APIs, no network calls.

## Install (MCPX / npx)

```bash
npx -y @mcpx-digital/timezone
```

> Prepared for npm as `@mcpx-digital/timezone`. Until published, run from a local clone.

## Cursor `mcp.json` example

```json
{
  "mcpServers": {
    "timezone": {
      "command": "npx",
      "args": ["-y", "@mcpx-digital/timezone"]
    }
  }
}
```

Local clone:

```json
{
  "mcpServers": {
    "timezone": {
      "command": "node",
      "args": ["/absolute/path/to/timezone-mcp/index.js"]
    }
  }
}
```

## Tools

| Tool | What it does |
|------|----------------|
| `convert_timezone` | Convert a moment between IANA zones |
| `what_time_when` | “What time is it in X when it’s Y in Z?” |
| `meeting_overlap` | Overlapping slots for N participants’ work hours |
| `list_common_zones` | Curated common IANA zone list |

## Example prompts

- “Convert 3pm UTC to America/Los_Angeles”
- “When it’s 9:00 in Tokyo, what time is it in New York on 2026-09-12?”
- “Find 30-minute meeting slots for NY 9–17 and London 9–17 on 2026-03-10”

## Development

```bash
git clone https://github.com/TheoryofShadows/timezone-mcp.git
cd timezone-mcp
npm install
npm test
node index.js
```

## Sell / list on MCPX

Suggested listing price: **$5**.

Install command: `npx -y @mcpx-digital/timezone`

## License

MIT © TheoryofShadows

TDQS

B3.3/5.0

Scored across 4 tools

Disambiguation3/5

convert_timezone and what_time_when both perform timezone conversions, making their boundaries blurry; descriptions hint at different input framing but overlap remains. list_common_zones and meeting_overlap are clearly distinct.

Naming Consistency3/5

All names use lower snake_case, but the structural pattern is mixed: convert_timezone and list_common_zones are verb-led, what_time_when is a question phrase, and meeting_overlap is noun-led. Readable but not predictably consistent.

Tool Count4/5

Four tools is a reasonable scope for a focused timezone utility, and each tool targets a plausible need. The pair of conversion tools is slightly redundant but not excessive.

Completeness4/5

Core timezone conversion, zone listing, and meeting overlap functionality are covered. Minor gaps remain, such as current-time-in-zone or zone lookup by city/offset, but these are workable around.

Maintenance

ActivityMaintained
ResponsivenessNo issues