findtime.io MCP Server

MCP server for time in cities around the world, time zones, DST, conversion, and meetings.

Connector by hkchao · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/hkchao-findtime-mcp-server

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

MCP server for time in cities around the world, time zones, DST, conversion, and meetings.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools: 11 read · 0 write · 0 deleteRead-only
Secrets: 1 (API keys, tokens or passwords)
Install scripts: Not scanned yet
Runs as: Node.js package

Tools by what they do 11

Read from the source code; the running server may list different tools.

Read 11 · Look things up without changing anything.

answer_time_question
convert_time
find_meeting_time
get_api_diagnostics
get_current_time
get_dst_schedule
get_findtime_help
get_location_by_id
get_overlap_hours
search_timezones
time_snapshot

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

FINDTIME_TIME_API_KEY

Other settings (environment variables or headers).

FINDTIME_MCP_CLIENT_TYPE
FINDTIME_TIME_API_BASE_URL

Tools (11)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

answer_time_questionread-only
PREFERRED entry point for vague, messy, or mixed time/timezone/scheduling questions. findtime.io classifies intent and dispatches internally. Use this when the user gives a raw natural-language prompt with a day or date qualifier, such as "Tuesday", "next Friday", "tomorrow", "tonight", "this weekend", "in 3 weeks", or "last Monday". If you already have structured arguments, the narrower tools can accept explicit ISO dates and simple human day/date values in their date fields where documented.
convert_timeread-only
Convert a source local time into one or more target locations using the production conversion endpoint. Use when you have structured source, target, and time arguments. date may be an explicit ISO calendar date (YYYY-MM-DD), or time may include a simple human date phrase such as "3pm Tuesday", "3pm thur", "3pm tomorrow", or "3pm next Friday"; findtime.io resolves that date relative to the source timezone. Route vague or mixed-intent raw prompts to answer_time_question. When presenting results, copy localTime.weekday, localTime.date, localTime.time12h/time24h, timezone abbreviation, and UTC off…
find_meeting_timeread-only
Return ranked meeting suggestions from the production meeting search endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Route vague or mixed-intent raw prompts to answer_time_question.
get_api_diagnosticsread-only
Return MCP and findtime Time API diagnostics, including the running MCP version, latest published MCP version, API base URL, auth configuration, and a live health check.
get_current_timeread-only
Return the production current time payload for a single city, query, or timezone. Exact country-name queries may be retried through a canonical city when the resolver can do so deterministically. For relative-date inputs ("Tuesday", "next Friday", "tomorrow", "tonight"), route to answer_time_question, which resolves the relative date and dispatches internally.
get_dst_scheduleread-only
Return the production DST schedule payload, including current abbreviation and transition details. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally.
get_findtime_helpread-only
Return enterprise-friendly findtime.io MCP usage help, including supported time-intelligence intents, answer API examples, ambiguity handling examples, and recommended answer-only deployment guidance.
get_location_by_idread-only
Hydrate an exact production location record by stable findtime id.
get_overlap_hoursread-only
Return shared business-hours overlap across multiple locations using the production overlap endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Route vague or mixed-intent raw prompts to answer_time_question.
search_timezonesread-only
Search production location records by city, country, or timezone-related query.
time_snapshotread-only
Return the production time snapshot payload for one location or a list of locations.

Signals

Stars: 0
Forks: 0
Open issues: 0
Weekly downloads: 61
Last commit: Sep 19, 2026 (1 month ago)
Last release: Sep 19, 2026 (1 month ago)
Last package publish: Sep 19, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name: io.github.hkchao/findtime-mcp-server
Version: 3.27.3
Auth: API key
Packages: npm @findtime/mcp-server
License: MIT
Repository: github.com/hkchao/findtime-mcp-server
Website: findtime.io
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql

Cite this page

findtime.io MCP Server. Agent Mart. https://agentmart.dev/connectors/hkchao-findtime-mcp-server (last updated 2026-10-24)