@chronary/mcp 0.1.3 → 1.0.1

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
@@ -2,7 +2,7 @@
2
2
 
3
3
  MCP server for [Chronary](https://chronary.ai) — calendar tools for AI assistants.
4
4
 
5
- Drops 23 calendar tools (list/create/update/delete events, check availability, manage webhooks, iCal subscriptions, usage) into any MCP-compatible client: Claude Desktop, Cursor, VS Code Copilot, Claude Code, Windsurf.
5
+ Drops 47 calendar tools (manage agents, calendars, and events, find meeting times, run scheduling proposals, configure availability rules, manage webhooks, iCal subscriptions, scoped keys, audit log, and usage) into any MCP-compatible client: Claude Desktop, Cursor, VS Code Copilot, Claude Code, Windsurf.
6
6
 
7
7
  ## Prerequisites
8
8
 
@@ -182,11 +182,11 @@ Edit `~/.codeium/windsurf/mcp_config.json` (`%USERPROFILE%\.codeium\windsurf\mcp
182
182
  }
183
183
  ```
184
184
 
185
- > **Windsurf limit:** Cascade enforces a hard cap of 100 total tools across all MCP servers and 20 tool calls per prompt. Chronary exposes 23; consider `--tools` filtering if you stack multiple servers.
185
+ > **Windsurf limit:** Cascade enforces a hard cap of 100 total tools across all MCP servers and 20 tool calls per prompt. Chronary exposes 47; consider `--tools` filtering if you stack multiple servers.
186
186
 
187
187
  ## Reducing context with `--tools`
188
188
 
189
- Exposing all 23 tools uses ~3–5k LLM tokens per request. For focused workflows, whitelist only what you need:
189
+ Exposing all 47 tools uses LLM tokens on every request. For focused workflows, whitelist only what you need:
190
190
 
191
191
  ```json
192
192
  {
@@ -195,7 +195,7 @@ Exposing all 23 tools uses ~3–5k LLM tokens per request. For focused workflows
195
195
  "command": "npx",
196
196
  "args": [
197
197
  "-y", "@chronary/mcp",
198
- "--tools", "list_events,check_availability,create_event"
198
+ "--tools", "list_events,find_meeting_time,create_event"
199
199
  ],
200
200
  "env": { "CHRONARY_API_KEY": "chr_sk_..." }
201
201
  }
@@ -221,15 +221,30 @@ For self-hosted Chronary instances or development against a local API:
221
221
  | `create_calendar`, `update_calendar` | | |
222
222
  | `delete_calendar` | | ✓ |
223
223
  | `list_events`, `get_event` | ✓ | |
224
- | `create_event`, `update_event` | | |
225
- | `delete_event` | | ✓ |
226
- | `check_availability` | ✓ | |
227
- | `list_webhooks`, `get_webhook` | | |
224
+ | `create_event`, `update_event`, `confirm_event` | | |
225
+ | `cancel_event`, `release_event` | | ✓ |
226
+ | `list_agents`, `get_agent` | ✓ | |
227
+ | `create_agent`, `update_agent` | | |
228
+ | `delete_agent` | | ✓ |
229
+ | `get_availability`, `find_meeting_time` | ✓ | |
230
+ | `get_calendar_context` | ✓ | |
231
+ | `list_proposals`, `get_proposal` | ✓ | |
232
+ | `create_proposal`, `respond_to_proposal`, `resolve_proposal` | | |
233
+ | `cancel_proposal` | | ✓ |
234
+ | `get_availability_rules` | ✓ | |
235
+ | `set_availability_rules` | | |
236
+ | `clear_availability_rules` | | ✓ |
237
+ | `list_webhooks`, `get_webhook`, `list_webhook_deliveries` | ✓ | |
228
238
  | `create_webhook`, `update_webhook` | | |
229
239
  | `delete_webhook` | | ✓ |
230
240
  | `list_ical_subscriptions`, `get_ical_subscription` | ✓ | |
231
- | `create_ical_subscription`, `update_ical_subscription`, `sync_ical_subscription` | | |
241
+ | `subscribe_ical`, `update_ical_subscription`, `sync_ical_subscription` | | |
232
242
  | `delete_ical_subscription` | | ✓ |
243
+ | `list_scoped_keys` | ✓ | |
244
+ | `create_scoped_key` | | |
245
+ | `revoke_scoped_key` | | ✓ |
246
+ | `get_audit_log` | ✓ | |
247
+ | `accept_terms` | | |
233
248
  | `get_usage` | ✓ | |
234
249
 
235
250
  Tool annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`) are surfaced to MCP clients so hosts can decide whether to require user confirmation.
package/dist/args.js CHANGED
@@ -64,8 +64,8 @@ Environment:
64
64
  CHRONARY_API_KEY Required. Your Chronary API key (chr_sk_...).
65
65
 
66
66
  Options:
67
- --tools <names> Comma-separated list of tool names to expose (default: all 23 tools).
68
- Example: --tools list_events,check_availability,create_event
67
+ --tools <names> Comma-separated list of tool names to expose (default: all 47 tools).
68
+ Example: --tools list_events,find_meeting_time,create_event
69
69
  --base-url <url> Override the API base URL (default: https://api.chronary.ai).
70
70
  --version, -v Print version and exit.
71
71
  --help, -h Print this help and exit.
package/dist/version.js CHANGED
@@ -1,2 +1,2 @@
1
- export const VERSION = '0.1.3';
1
+ export const VERSION = '1.0.1';
2
2
  //# sourceMappingURL=version.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@chronary/mcp",
3
- "version": "0.1.3",
3
+ "version": "1.0.1",
4
4
  "description": "MCP server for Chronary — calendar tools for AI assistants (Claude Desktop, Cursor, VS Code, Windsurf)",
5
5
  "license": "Apache-2.0",
6
6
  "type": "module",
@@ -31,7 +31,7 @@
31
31
  "type": "git",
32
32
  "url": "https://github.com/Chronary/chronary-mcp"
33
33
  },
34
- "homepage": "https://docs.chronary.ai",
34
+ "homepage": "https://chronary.ai",
35
35
  "bugs": {
36
36
  "url": "https://github.com/Chronary/chronary-mcp/issues"
37
37
  },
@@ -39,15 +39,15 @@
39
39
  "access": "public"
40
40
  },
41
41
  "dependencies": {
42
- "@chronary/sdk": "^0.1.4",
43
- "@chronary/toolkit": "^0.1.3",
42
+ "@chronary/sdk": "^0.3.1",
43
+ "@chronary/toolkit": "^1.0.1",
44
44
  "@modelcontextprotocol/sdk": "^1.29.0",
45
- "zod": "^3.23"
45
+ "zod": "^4.4"
46
46
  },
47
47
  "devDependencies": {
48
- "@types/node": "^22.0.0",
48
+ "@types/node": "^25.9.1",
49
49
  "typescript": "^5.7.0",
50
- "vitest": "^3.0.0"
50
+ "vitest": "^4.1.8"
51
51
  },
52
52
  "scripts": {
53
53
  "build": "tsc",