timezest-mcp 1.0.0 → 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 +88 -0
- package/package.json +11 -2
package/README.md
ADDED
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# 📅 TimeZest MCP Server
|
|
2
|
+
|
|
3
|
+
An MCP (Model Context Protocol) server that brings **TimeZest** scheduling data (confirmed appointments, pending invitations, and ticket-linked schedules) directly into your Claude conversations.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## 📋 Prerequisites (One-Time Setup)
|
|
8
|
+
|
|
9
|
+
Before you begin, ensure you have **Node.js** installed on your machine. This is what allows Claude to run the server.
|
|
10
|
+
|
|
11
|
+
1. **Download Node.js**: [Download here (v18 or higher recommended)](https://nodejs.org/)
|
|
12
|
+
2. **Verify**: Open a terminal and type `node -v` to confirm it's installed.
|
|
13
|
+
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
## 🚀 How to Install (For Colleagues)
|
|
17
|
+
|
|
18
|
+
You don't need to download or build any code. You can run this directly using `npx`.
|
|
19
|
+
|
|
20
|
+
### Option A — Claude Desktop (Standard)
|
|
21
|
+
Open your Claude Desktop configuration file:
|
|
22
|
+
- **Windows:** `%AppData%\Roaming\Claude\claude_desktop_config.json`
|
|
23
|
+
- **Mac:** `~/Library/Application Support/Claude/claude_desktop_config.json`
|
|
24
|
+
|
|
25
|
+
Add this entry to the `mcpServers` section:
|
|
26
|
+
|
|
27
|
+
```json
|
|
28
|
+
{
|
|
29
|
+
"mcpServers": {
|
|
30
|
+
"timezest": {
|
|
31
|
+
"command": "npx",
|
|
32
|
+
"args": ["-y", "timezest-mcp@latest"],
|
|
33
|
+
"env": {
|
|
34
|
+
"TIMEZEST_API_KEY": "YOUR_API_KEY_HERE",
|
|
35
|
+
"TIMEZEST_DEFAULT_TZ": "America/Chicago"
|
|
36
|
+
}
|
|
37
|
+
}
|
|
38
|
+
}
|
|
39
|
+
}
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
### Option B — Claude Code (CLI)
|
|
43
|
+
If you use the terminal-based **Claude Code**, run this single command to add the server globally:
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
claude mcp add-json timezest "{\"type\": \"stdio\", \"command\": \"npx\", \"args\": [\"-y\", \"timezest-mcp@latest\"], \"env\": {\"TIMEZEST_API_KEY\": \"YOUR_API_KEY_HERE\", \"TIMEZEST_DEFAULT_TZ\": \"America/Chicago\"}}"
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
## 💡 Example Prompts
|
|
52
|
+
Once connected, try asking Claude:
|
|
53
|
+
- *"What's the briefing for today?"*
|
|
54
|
+
- *"Show me Aaron's schedule for next week"*
|
|
55
|
+
- *"Find any TimeZest requests for ticket #964400"*
|
|
56
|
+
- *"Who has the oldest pending invitations?"*
|
|
57
|
+
- *"Give me the appointment stats for the last 14 days"*
|
|
58
|
+
- *"Show me recently cancelled appointments for Isam"*
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## 🛠️ Available Tools
|
|
63
|
+
|
|
64
|
+
| Tool | What It Does |
|
|
65
|
+
|------|-------------|
|
|
66
|
+
| `get_todays_appointments` | Morning briefing: Confirmed today vs. pending unbooked |
|
|
67
|
+
| `list_appointments` | Flexible range search with engineer and status filters |
|
|
68
|
+
| `get_engineer_schedule` | Sorted timeline for a specific engineer |
|
|
69
|
+
| `list_pending_requests` | Follow up on `sent` and `new` (unbooked) invitations |
|
|
70
|
+
| `find_appointment_by_ticket` | Instant lookup using ConnectWise ticket numbers |
|
|
71
|
+
| `get_appointment_types` | List all available scheduling types (ID vs Name) |
|
|
72
|
+
| `get_appointment_stats` | Management summary: Counts, minutes, and oldest pending |
|
|
73
|
+
| `list_cancelled_appointments` | Triage cancelled requests for rebooking |
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
## 📦 Technical Info
|
|
78
|
+
- **Package Name:** `timezest-mcp`
|
|
79
|
+
- **Platform:** Node.js (v18+)
|
|
80
|
+
- **Environment Variables**:
|
|
81
|
+
- `TIMEZEST_API_KEY` (Required): Your TimeZest Bearer token.
|
|
82
|
+
- `TIMEZEST_DEFAULT_TZ` (Optional): Default IANA timezone (e.g. `America/Chicago`).
|
|
83
|
+
- **Developer:** Sagar Kalra
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
87
|
+
## 📄 License
|
|
88
|
+
MIT © 2026 Sagar Kalra.
|
package/package.json
CHANGED
|
@@ -1,8 +1,17 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "timezest-mcp",
|
|
3
|
-
"version": "1.0.
|
|
4
|
-
"description": "MCP Server for TimeZest scheduling API",
|
|
3
|
+
"version": "1.0.1",
|
|
4
|
+
"description": "MCP Server for TimeZest scheduling API — brings appointments, pending requests, and ticket-linked schedules to Claude.",
|
|
5
5
|
"main": "build/index.js",
|
|
6
|
+
"author": "Sagar Kalra",
|
|
7
|
+
"keywords": [
|
|
8
|
+
"mcp",
|
|
9
|
+
"model-context-protocol",
|
|
10
|
+
"timezest",
|
|
11
|
+
"scheduling",
|
|
12
|
+
"connectwise",
|
|
13
|
+
"msp"
|
|
14
|
+
],
|
|
6
15
|
"type": "module",
|
|
7
16
|
"bin": {
|
|
8
17
|
"timezest-mcp": "build/index.js"
|