
Timezest Mcp
io.github.sagarkalra-tech由 GitHub 帳號 sagarkalra-tech 發布v1.1.0更新於 Oct 24, 2026
MCP Server for TimeZest: manage appointments, pending requests, and ticket schedules in Claude.
概覽
一個唯讀的 MCP 伺服器,把 TimeZest 排程資料帶進助理:預約、待處理請求、工程師行程和關聯工單的預約。
- 可以做什麼
- 依日期範圍、工程師、狀態或 ConnectWise 工單編號查詢預約,並取得依工程師分組的當日已確認預約晨間簡報,同時列出待處理的未預約請求。檢視待處理和已取消的排程請求,包括已等待多久以及取消請求的重新預約連結。查看某位工程師接下來的行程,並列出 TimeZest 中設定的預約類型。產生彙總排程統計,例如依狀態和工程師的計數、當日負載和最久未處理的請求,並附上時區準確的顯示文字。
- 適用情境
- 適合同時使用 TimeZest 和 ConnectWise 的團隊,想用自然語言查詢預約、追蹤未預約請求並檢視團隊排程負載,而不必在多个分頁之間切換。
- 執行需求
- 透過 npm 套件 timezest-mcp 以 stdio 在本機執行,需要 Node.js 20 或更新版本。必須在 TIMEZEST_API_KEY 環境變數中提供 TimeZest API 金鑰;選用變數可設定預設 IANA 時區以及往前、往後的查詢範圍。需要連線至 TimeZest API 的網路存取。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Timezest Mcp,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
⏰ TimeZest MCP Server
[npm version] [MCP Registry] [CI] [License: MIT]
Bring your TimeZest scheduling data directly into Claude through the Model Context Protocol (MCP). Perform real-time appointment lookups, engineer briefings, and ticket-linked schedule management — all with natural language.
Registry ID: io.github.sagarkalra-tech/timezest-mcp
🌟 Why TimeZest MCP?
If you manage a team that uses TimeZest with ConnectWise, you know the pain: toggling between tabs, manually checking who's booked, chasing unbooked scheduling requests, and cross-referencing ticket numbers.
This MCP server turns Claude into a scheduling assistant that can:
- 🗓️ Give you a morning briefing of today's confirmed appointments grouped by engineer
- 🔍 Find appointments by ticket number — just say "find appointments for ticket #964400"
- ⏳ Surface aging unbooked requests that need follow-up
- 📊 Generate aggregate scheduling stats across your team
- 🕐 Handle timezone-accurate reporting across global MSP teams
🚀 Get Started in 30 Seconds
Prerequisites
- Node.js 20+ — Download here
- TimeZest API Key — Found in TimeZest → Settings → API
Option 1: Claude Desktop (Recommended)
Add this to your Claude Desktop configuration file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Restart Claude Desktop. You're done.
Option 2: Claude Code CLI
Option 3: VS Code (Copilot)
Add to your .vscode/settings.json or User Settings:
🛠️ Available Tools
The server exposes 8 specialized tools that Claude can call:
💬 Example Prompts
Once connected, just talk to Claude naturally:
⚙️ Configuration
🏗️ Architecture
Key Design Decisions
- Read-Only: Intentionally kept read-only — no mutations to your scheduling data
- Resilient Client: Exponential backoff with automatic
Retry-Afterheader support for 429/5xx errors - Deep Pagination: Recursively crawls all pages (50-item chunks) to build complete datasets
- Timezone Precision: Converts Unix timestamps to strict ISO with localized display strings using IANA timezone identifiers
- Engineer Resolution: Uses a "highest-confidence" search — checks
scheduled_agentsfirst, then falls back toresources - Warm Cache: Appointment types are cached after first fetch to reduce API overhead
🧪 Testing
The server ships with a comprehensive Vitest test suite — 22 tests across 3 files:
All tests use mocked API responses — no live API calls, no secrets needed.
🔒 Security & Trust
- NPM Provenance: Every release is cryptographically signed via GitHub Actions OIDC
- CI/CD Pipeline: Automated build → test → publish on tagged releases (no manual
npm publish) - No Secrets in CI: Tests require no API keys — fully deterministic with mocked responses
- Node.js Matrix: Tested on Node 20 (LTS) and 22 (Current)
📦 Distribution
🤝 Contributing
- Fork the repository
- Create a feature branch (
git checkout -b feat/my-feature) - Make your changes and ensure tests pass (
npm test) - Submit a pull request
See ARCHITECTURE.md for a deep dive into the data flow, component design, and transformation logic.
📄 License
MIT © 2026 Sagar Kalra
來源:README.md,提交 766cd8b
工具
0版本歷史
1- v1.1.0最新Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。