
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 分
请在仓库或注册中心条目中声明许可证。