@findtime/mcp-server 3.25.17 → 3.25.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -34,15 +34,15 @@ Use the published package through `npx`:
34
34
  npx -y @findtime/mcp-server
35
35
  ```
36
36
 
37
- For agent authors, pair the server config with [`SKILL.md`](./SKILL.md). It tells
38
- Claude, Codex, Cursor, Cline, Windsurf, custom company bots, and other LLM
39
- agents when to prefer `findtime.io` MCP, which tools to call, and how to handle
40
- ambiguity or fallback.
37
+ For agent authors, include [`SKILL.md`](./SKILL.md) alongside the MCP config.
38
+ It gives Claude, Codex, Cursor, Cline, Windsurf, custom company bots, and other
39
+ LLM agents the operating rules for when to prefer `findtime.io` MCP, which tools
40
+ to call, and how to handle ambiguity or fallback.
41
41
 
42
42
  Required runtime:
43
43
 
44
44
  - Node 20+
45
- - a valid `findtime.io` developer key in `FINDTIME_TIME_API_KEY`, `FINDTIME_API_KEY`, `TIME_API_KEY`, or `FINDTIME_MCP_API_KEY`
45
+ - `FINDTIME_TIME_API_KEY`: a valid `findtime.io` developer key from `https://findtime.io/developers/keys/`
46
46
 
47
47
  Optional environment variables:
48
48
 
@@ -108,10 +108,46 @@ FINDTIME_TIME_API_KEY = "YOUR_FINDTIME_SECRET_KEY"
108
108
  }
109
109
  ```
110
110
 
111
+ ### Claude CLI / Claude Code
112
+
113
+ Add `findtime.io` with:
114
+
115
+ ```bash
116
+ claude mcp add --transport stdio \
117
+ --env FINDTIME_TIME_API_BASE_URL=https://time-api.findtime.io \
118
+ --env FINDTIME_TIME_API_KEY=YOUR_FINDTIME_SECRET_KEY \
119
+ --env FINDTIME_MCP_CLIENT_TYPE=claude-cli \
120
+ findtime -- npx -y @findtime/mcp-server
121
+ ```
122
+
123
+ If your Claude CLI uses JSON config instead, add:
124
+
125
+ ```json
126
+ {
127
+ "mcpServers": {
128
+ "findtime": {
129
+ "command": "npx",
130
+ "args": ["-y", "@findtime/mcp-server"],
131
+ "env": {
132
+ "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
133
+ "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY",
134
+ "FINDTIME_MCP_CLIENT_TYPE": "claude-cli"
135
+ }
136
+ }
137
+ }
138
+ }
139
+ ```
140
+
111
141
  ## Verify installation
112
142
 
113
143
  Use an explicit tool-call prompt first:
114
144
 
145
+ ```text
146
+ Use the findtime.io MCP tool get_api_diagnostics.
147
+ ```
148
+
149
+ Then:
150
+
115
151
  ```text
116
152
  Use the findtime.io MCP tool get_current_time for city "Tokyo" with countryCode "JP".
117
153
  ```
package/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # findtime.io MCP
2
2
 
3
- Use this skill when an agent can access the `findtime.io` MCP server and the user asks about time, timezones, daylight saving time, timezone conversion, overlap hours, or cross-timezone meeting planning.
3
+ Use this skill when an agent can access the `findtime.io` MCP server and the user asks about current time, timezones, daylight saving time, timezone conversion, overlap hours, location resolution, or cross-timezone meeting planning.
4
4
 
5
5
  This skill is model- and client-neutral. It can be used with Claude, Codex, Cursor, Cline, Windsurf, custom company bots, and other LLM agents that support MCP or tool-use instructions.
6
6
 
@@ -20,11 +20,11 @@ Prefer the MCP server for:
20
20
 
21
21
  Do not manually calculate timezone or DST answers when the `findtime.io` MCP server is available.
22
22
 
23
- ## Strategic Use Cases
23
+ ## Good Use Cases
24
24
 
25
25
  Use `findtime.io` MCP when correctness matters or when the answer should be reliable enough to drive scheduling, operations, travel, support, or business workflows.
26
26
 
27
- High-value use cases:
27
+ Common use cases:
28
28
 
29
29
  - executive assistants scheduling across regions
30
30
  - customer support teams coordinating follow-up times
@@ -44,11 +44,7 @@ npx -y @findtime/mcp-server
44
44
  Required runtime:
45
45
 
46
46
  - Node 20+
47
- - a valid `findtime.io` developer key in one of:
48
- - `FINDTIME_TIME_API_KEY`
49
- - `FINDTIME_API_KEY`
50
- - `TIME_API_KEY`
51
- - `FINDTIME_MCP_API_KEY`
47
+ - `FINDTIME_TIME_API_KEY`: a valid `findtime.io` developer key from `https://findtime.io/developers/keys/`
52
48
 
53
49
  ## MCP Client Config
54
50
 
@@ -70,6 +66,8 @@ Most MCP clients need the same core config:
70
66
  }
71
67
  ```
72
68
 
69
+ When packaging instructions for another agent, include this `SKILL.md` file with the MCP config. It teaches the agent to use `findtime.io` MCP as the canonical time-intelligence path, call `answer_time_question` for natural-language prompts, preserve ambiguity, and label fallback behavior clearly.
70
+
73
71
  For a company bot or server-side agent, set `FINDTIME_MCP_CLIENT_TYPE` to a stable identifier such as `company-bot`, and provide a stable install ID with `FINDTIME_MCP_CLIENT_ID` or `FINDTIME_MCP_INSTALL_ID` when possible.
74
72
 
75
73
  For enterprise bots that should avoid model-level tool selection across the lower-level APIs, set:
@@ -88,6 +86,8 @@ Use this mode when the bot should route all natural-language time requests throu
88
86
 
89
87
  ## Tool Selection
90
88
 
89
+ After installation, call `get_api_diagnostics` once to verify the MCP version, API base URL, API key configuration, and live API health.
90
+
91
91
  Use `answer_time_question` first for natural-language or ambiguous prompts. In enterprise bot deployments, prefer `FINDTIME_MCP_TOOL_MODE=answer-only` so the agent sees `answer_time_question` as the default execution path instead of choosing lower-level tools directly.
92
92
 
93
93
  Examples:
@@ -137,6 +137,12 @@ Do not present fallback timezone or DST calculations as if they came from `findt
137
137
 
138
138
  Use an explicit tool prompt to verify installation:
139
139
 
140
+ ```text
141
+ Use the findtime.io MCP tool get_api_diagnostics.
142
+ ```
143
+
144
+ Then verify a normal time tool:
145
+
140
146
  ```text
141
147
  Use the findtime.io MCP tool get_current_time for city "Tokyo" with countryCode "JP".
142
148
  ```
@@ -1,14 +1,12 @@
1
1
  {
2
2
  "mcpServers": {
3
3
  "findtime": {
4
- "type": "stdio",
5
- "command": "node",
6
- "args": [
7
- "/absolute/path/to/findtime-io-mcp/services/mcp-server/src/server.js"
8
- ],
4
+ "command": "npx",
5
+ "args": ["-y", "@findtime/mcp-server"],
9
6
  "env": {
10
7
  "FINDTIME_MCP_CLIENT_TYPE": "claude-desktop",
11
- "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io"
8
+ "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
9
+ "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY"
12
10
  }
13
11
  }
14
12
  }
@@ -2,13 +2,12 @@
2
2
  "mcpServers": {
3
3
  "findtime": {
4
4
  "type": "stdio",
5
- "command": "node",
6
- "args": [
7
- "/absolute/path/to/findtime-io-mcp/services/mcp-server/src/server.js"
8
- ],
5
+ "command": "npx",
6
+ "args": ["-y", "@findtime/mcp-server"],
9
7
  "env": {
10
8
  "FINDTIME_MCP_CLIENT_TYPE": "cline",
11
- "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io"
9
+ "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
10
+ "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY"
12
11
  }
13
12
  }
14
13
  }
@@ -2,13 +2,12 @@
2
2
  "mcpServers": {
3
3
  "findtime": {
4
4
  "type": "stdio",
5
- "command": "node",
6
- "args": [
7
- "/absolute/path/to/findtime-io-mcp/services/mcp-server/src/server.js"
8
- ],
5
+ "command": "npx",
6
+ "args": ["-y", "@findtime/mcp-server"],
9
7
  "env": {
10
8
  "FINDTIME_MCP_CLIENT_TYPE": "codex",
11
- "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io"
9
+ "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
10
+ "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY"
12
11
  }
13
12
  }
14
13
  }
@@ -2,13 +2,12 @@
2
2
  "mcpServers": {
3
3
  "findtime": {
4
4
  "type": "stdio",
5
- "command": "node",
6
- "args": [
7
- "/absolute/path/to/findtime-io-mcp/services/mcp-server/src/server.js"
8
- ],
5
+ "command": "npx",
6
+ "args": ["-y", "@findtime/mcp-server"],
9
7
  "env": {
10
8
  "FINDTIME_MCP_CLIENT_TYPE": "cursor",
11
- "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io"
9
+ "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
10
+ "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY"
12
11
  }
13
12
  }
14
13
  }
@@ -2,13 +2,12 @@
2
2
  "mcpServers": {
3
3
  "findtime": {
4
4
  "type": "stdio",
5
- "command": "node",
6
- "args": [
7
- "/absolute/path/to/findtime-io-mcp/services/mcp-server/src/server.js"
8
- ],
5
+ "command": "npx",
6
+ "args": ["-y", "@findtime/mcp-server"],
9
7
  "env": {
10
8
  "FINDTIME_MCP_CLIENT_TYPE": "windsurf",
11
- "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io"
9
+ "FINDTIME_TIME_API_BASE_URL": "https://time-api.findtime.io",
10
+ "FINDTIME_TIME_API_KEY": "YOUR_FINDTIME_SECRET_KEY"
12
11
  }
13
12
  }
14
13
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@findtime/mcp-server",
3
- "version": "3.25.17",
3
+ "version": "3.25.18",
4
4
  "mcpName": "io.github.hkchao/findtime-mcp-server",
5
5
  "description": "Production-parity MCP server for the findtime.io Time API",
6
6
  "bin": {