Findtime MCP Server

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

Local serverstdio

What is the Findtime MCP server?

If you already use Findtime, the findtime mcp server is the piece that lets your assistant work with it directly. MCP server for time in cities around the world, time zones, DST, conversion, and meetings.

What the server does

@findtime/mcp-server is a thin stdio MCP wrapper over the production findtime.io Time API at https://time-api.findtime.io.

Installation

The server ships on npm as @findtime/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • GitHubhttps://github.com/hkchao/findtime-mcp-server
  • answer_time_question — get_findtime_help
  • time_snapshot — get_current_time
  • get_dst_schedule — convert_time
  • get_overlap_hours — find_meeting_time
  • search_timezones — get_location_by_id
  • FINDTIME_TIME_API_KEY — a valid findtime.io developer key from https://findtime.io/developers/keys/
  • FINDTIME_TIME_API_BASE_URL — TIME_API_BASE_URL
  • TIME_API_TIMEOUT_MS — FINDTIME_BINDING_TYPE for optional install/workspace binding context. Supported values: slack_team, workspace_id, install_id
  • FINDTIME_MCP_CLIENT_TYPE — FINDTIME_MCP_TOOL_MODE=answer-only to expose only answer_time_question, get_findtime_help, and get_api_diagnostics for enterprise bots that should
  • get_current_time — get_dst_schedule
  • convert_time — get_overlap_hours

Credentials and setup notes

Configuration is passed through the environment: FINDTIME_MCP_CLIENT_TYPE, FINDTIME_TIME_API_BASE_URL, FINDTIME_TIME_API_KEY, TIME_API_BASE_URL, FINDTIME_MCP_CLIENT_ID, FINDTIME_MCP_INSTALL_ID, FINDTIME_MCP_USAGE_TELEMETRY_URL, YOUR_FINDTIME_SECRET_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Findtime.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Findtime's toolset — GitHub, answer_time_question, time_snapshot and 11 more — is a fair guide to whether it matches your workflow. It is maintained by hkchao; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Findtime's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
GitHubhttps://github.com/hkchao/findtime-mcp-server
answer_time_questionget_findtime_help
time_snapshotget_current_time
get_dst_scheduleconvert_time
get_overlap_hoursfind_meeting_time
search_timezonesget_location_by_id
FINDTIME_TIME_API_KEYa valid findtime.io developer key from https://findtime.io/developers/keys/
FINDTIME_TIME_API_BASE_URLTIME_API_BASE_URL
TIME_API_TIMEOUT_MSFINDTIME_BINDING_TYPE for optional install/workspace binding context. Supported values: slack_team, workspace_id, install_id.
FINDTIME_MCP_CLIENT_TYPEFINDTIME_MCP_TOOL_MODE=answer-only to expose only answer_time_question, get_findtime_help, and get_api_diagnostics for enterprise bots that should route every natural-language request through the answer API.
get_current_timeget_dst_schedule
convert_timeget_overlap_hours
find_meeting_timeget_location_by_id
CursorThe Cursor tool exposed by this server.

How to install the Findtime MCP server

{
  "preferences": {
    "...": "keep your existing preferences here"
  },
  "mcpServers": {
    "findtime": {
      "command": "npx",
      "args": ["-y", "@findtime/mcp-server"],
        "env": {
          "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
          "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY"
        }
      }
    }
  }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
FINDTIME_MCP_CLIENT_TYPEConfiguration value read at startup.Optional
FINDTIME_TIME_API_BASE_URLEndpoint or connection string the server talks to.Yes
FINDTIME_TIME_API_KEYCredential the server authenticates with.Yes
TIME_API_BASE_URLEndpoint or connection string the server talks to.Yes
FINDTIME_MCP_CLIENT_IDConfiguration value read at startup.Optional
FINDTIME_MCP_INSTALL_IDConfiguration value read at startup.Optional
FINDTIME_MCP_USAGE_TELEMETRY_URLEndpoint or connection string the server talks to.Yes
YOUR_FINDTIME_SECRET_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Findtime to GitHub.
  • Use Findtime to answer time question.
  • Use Findtime to time snapshot.

Frequently asked questions

It connects Findtime to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (GitHub, answer_time_question, time_snapshot, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Findtime directly.