@findtime/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIME_API_KEY | No | A valid findtime.io developer key (alias for FINDTIME_TIME_API_KEY). | |
| FINDTIME_API_KEY | No | A valid findtime.io developer key (alias for FINDTIME_TIME_API_KEY). | |
| TIME_API_BASE_URL | No | Base URL for the Time API (alias for FINDTIME_TIME_API_BASE_URL). | |
| TIME_API_TIMEOUT_MS | No | Timeout for Time API calls in milliseconds. | |
| FINDTIME_MCP_API_KEY | No | A valid findtime.io developer key (alias for FINDTIME_TIME_API_KEY). | |
| FINDTIME_BINDING_TYPE | No | Binding type for enterprise install context. Supported values: slack_team, workspace_id, install_id. | |
| FINDTIME_TIME_API_KEY | No | A valid findtime.io developer key from https://findtime.io/developers/keys/. | |
| FINDTIME_BINDING_VALUE | No | The install/workspace identifier that matches the selected binding type. | |
| FINDTIME_MCP_CLIENT_ID | No | Stable client identifier for enterprise usage attribution (forwarded as X-Findtime-User-ID). | |
| FINDTIME_MCP_TOOL_MODE | No | Set to 'answer-only' to expose only answer_time_question, get_findtime_help, and get_api_diagnostics. | |
| FINDTIME_BINDING_HEADER | No | Override the header name used for binding context in custom enterprise environments. | |
| FINDTIME_MCP_INSTALL_ID | No | Stable install identifier for enterprise usage attribution (alternative to FINDTIME_MCP_CLIENT_ID). | |
| FINDTIME_MCP_CLIENT_TYPE | No | Client type, e.g., cursor, codex, claude-cli. | |
| FINDTIME_TIME_API_BASE_URL | No | Base URL for the Time API (default: https://time-api.findtime.io). | |
| FINDTIME_MCP_USAGE_TELEMETRY_URL | No | Override the default telemetry endpoint. | |
| FINDTIME_MCP_INSTRUMENTATION_ENABLED | No | Set to 'false' to opt out of anonymous usage telemetry. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| answer_time_questionA | PREFERRED entry point for time/timezone/scheduling questions. findtime.io classifies intent and dispatches internally. Use this WHENEVER the user's input includes a natural-language day or date qualifier, such as "Tuesday", "next Friday", "tomorrow", "tonight", "this weekend", "in 3 weeks", or "last Monday". The specific tools (convert_time, get_current_time, find_meeting_time, etc.) will silently drop these qualifiers if you dispatch to them without an explicit ISO date. Also the right choice for vague or mixed-intent prompts. |
| get_api_diagnosticsA | 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_findtime_helpB | 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. |
| time_snapshotC | Return the production time snapshot payload for one location or a list of locations. |
| get_current_timeA | 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_scheduleA | 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. |
| convert_timeA | Convert a source local time into one or more target locations using the production conversion endpoint. Use ONLY when date is an explicit ISO calendar date (YYYY-MM-DD) you can pass in, OR the conversion is for the current moment with no date qualifier at all. DO NOT use this tool if the user said "Tuesday", "tomorrow", "next Friday", or any other relative day/date phrase; those qualifiers will be silently dropped here. Route to answer_time_question instead, which parses relative dates correctly. When presenting results, copy localTime.weekday, localTime.date, localTime.time12h/time24h, timezone abbreviation, and UTC offset exactly from the tool output; do not recompute or shift day names during synthesis. |
| get_overlap_hoursA | Return shared business-hours overlap across multiple locations using the production overlap endpoint. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally. |
| find_meeting_timeA | Return ranked meeting suggestions from the production meeting search endpoint. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally. |
| search_timezonesB | Search production location records by city, country, or timezone-related query. |
| get_location_by_idA | Hydrate an exact production location record by stable findtime id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Tools are well-differentiated with clear instructions. The answer_time_question tool is explicitly designated for relative-date queries, while specific tools like convert_time, get_current_time, and find_meeting_time are for exact dates or current moment. Some potential confusion between time_snapshot and get_current_time, which both return time-related payloads, but descriptions help distinguish them.
Most tools follow a verb_noun pattern (get_current_time, convert_time, search_timezones, etc.). One deviation is time_snapshot, which is noun_verb, and answer_time_question follows the pattern. Overall, the naming is consistent and readable, with only a minor deviation.
11 tools is a reasonable number for a time-intelligence server. The set includes core operations (conversion, current time, overlap, meeting time), utility (search, location lookup), diagnostics, help, and an entry point. There is slight redundancy between time_snapshot and get_current_time, but the count is not excessive or insufficient.
The tool set covers the major time-related workflows: current time, conversion, DST schedule, overlap, meeting suggestions, and location resolution. It also includes diagnostics and help for enterprise deployment. It lacks some advanced features like timezone math or calendar integration, but for its stated purpose it appears comprehensive.