Timezest MCP

MCP Server for TimeZest: manage appointments, pending requests, and ticket schedules in Claude.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "timezest-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "timezest-mcp@latest"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

⏰ TimeZest MCP Server

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

config.json

{
  "mcpServers": {
    "timezest": {
      "command": "npx",
      "args": ["-y", "timezest-mcp@latest"],
      "env": {
        "TIMEZEST_API_KEY": "your-timezest-api-key-here"
      }
    }
  }
}

Restart Claude Desktop. You're done.

Option 2: Claude Code CLI

Terminal

claude mcp add-json timezest-mcp '{
  "command": "npx",
  "args": ["-y", "timezest-mcp@latest"],
  "env": {
    "TIMEZEST_API_KEY": "your-timezest-api-key-here"
  }
}'

Option 3: VS Code (Copilot)

Add to your .vscode/settings.json or User Settings:

config.json

{
  "mcp": {
    "servers": {
      "timezest": {
        "command": "npx",
        "args": ["-y", "timezest-mcp@latest"],
        "env": {
          "TIMEZEST_API_KEY": "your-timezest-api-key-here"
        }
      }
    }
  }
}

🛠️ Available Tools

The server exposes 8 specialized tools that Claude can call:

Tool	Description	Key Parameters
`get_todays_appointments`	Morning briefing — today's confirmed appointments grouped by engineer, plus pending unbooked requests	`timezone`
`list_appointments`	Flexible query across any date range with optional filters	`start_date`, `end_date`, `engineer_name`, `status`
`get_engineer_schedule`	All upcoming appointments for a specific engineer, sorted by time	`engineer_name`, `days_ahead`, `include_pending`
`list_pending_requests`	Unbooked invitations (sent/new) with age tracking in hours/days	`days_back`, `engineer_name`, `older_than_hours`
`find_appointment_by_ticket`	Find appointments linked to a ConnectWise ticket number	`ticket_number` (e.g., `964400` or `#964400`)
`get_appointment_types`	List all appointment type definitions configured in TimeZest	—
`get_appointment_stats`	Aggregate summary: counts by status, by engineer, today's load, oldest pending	`days_back`, `days_forward`
`list_cancelled_appointments`	Cancelled requests with scheduling URLs for rebooking	`days_back`, `engineer_name`

💬 Example Prompts

Once connected, just talk to Claude naturally:

Code

"Who are my top engineers today and what are they booked for?"

"Find any TimeZest requests for ticket #964400."

"Give me a morning briefing of today's confirmed vs. unbooked requests."

"Show me all pending scheduling requests older than 48 hours."

"What's the scheduling volume breakdown for the last two weeks?"

"Pull up Sarah's schedule for the next 5 days."

"List all cancelled appointments from last week — any we should rebook?"

⚙️ Configuration

Environment Variable	Required	Default	Purpose
`TIMEZEST_API_KEY`	Yes	—	Your TimeZest Bearer token (Settings → API)
`TIMEZEST_DEFAULT_TZ`	No	`America/Chicago`	Default IANA timezone for localized display strings
`TIMEZEST_WINDOW_DAYS_BACK`	No	`14`	How many days back to fetch scheduling requests
`TIMEZEST_WINDOW_DAYS_FORWARD`	No	`30`	How many days forward to fetch scheduling requests

🏗️ Architecture

Code

┌─────────────────────────────────────────────────────────────────┐
│                        MCP CLIENT (Claude)                      │
│        Desktop App  •  Claude Code CLI  •  IDE Plugin           │
└──────────────────────────┬──────────────────────────────────────┘
                           │ Stdio (JSON-RPC)
┌──────────────────────────▼──────────────────────────────────────┐
│                     TIMEZEST MCP SERVER                         │
│                                                                 │
│  ┌──────────────┐  ┌──────────────┐                             │
│  │ Tool Handler │  │  MCP SDK     │  (index.ts)                 │
│  │ (8 Tools)    │  │  Registry    │                             │
│  └──────┬───────┘  └──────────────┘                             │
│         │                                                       │
│  ┌──────▼────────────────────────────────────────────────────┐  │
│  │                 TIMEZEST API CLIENT                        │  │
│  │  Pagination • Retry Logic • Rate Limit Management         │  │
│  └──────────────────────┬────────────────────────────────────┘  │
│                         │ (client.ts)                            │
│  ┌──────────────────────▼────────────────────────────────────┐  │
│  │               DATA TRANSFORMATION LAYER                    │  │
│  │  Timezone Math • Engineer Mapping • Ticket Linking         │  │
│  └────────────────────────────────────────────────────────────┘  │
│                         │ (utils/)                               │
└─────────────────────────┼────────────────────────────────────────┘
                          │ HTTPS / REST
┌─────────────────────────▼──────────────────────────────────────┐
│                      TIMEZEST API (v1)                          │
│       Scheduling Requests • Appointment Types • Resources       │
└─────────────────────────────────────────────────────────────────┘

Key Design Decisions

Read-Only: Intentionally kept read-only — no mutations to your scheduling data
Resilient Client: Exponential backoff with automatic Retry-After header 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_agents first, then falls back to resources
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:

Test File	Tests	Coverage
`transform.test.ts`	8	Engineer resolution, ticket extraction, timezone conversion, graceful handling of missing fields
`filter.test.ts`	6	Case-insensitive partial matching, team name matching, date-range filtering
`client.test.ts`	8	Appointment type caching, pagination, retry on 429/5xx, no-retry on 4xx

All tests use mocked API responses — no live API calls, no secrets needed.

Terminal

npm test            # Single run
npm run test:watch  # Re-runs on file save

🔒 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

Channel	Link
NPM	`timezest-mcp`
MCP Registry	`io.github.sagarkalra-tech/timezest-mcp`
GitHub	`sagarkalra-tech/TimeZest-MCP`

🤝 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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

192

Package downloads in the last 30 days.

Last commit

5mo ago

Most recent push to the default branch.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Timezest MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "timezest-mcp": { "command": "npx", "args": ["-y", "timezest-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/timezest-mcp?style=directory)](https://allmcps.com/mcp/timezest-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/timezest-mcp"><img src="https://allmcps.com/api/badge/timezest-mcp?style=directory" alt="Timezest MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

40Quality signal: Fair · 40/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity4/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Timezest MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Timezest MCP

MCP Server for TimeZest: manage appointments, pending requests, and ticket schedules in Claude.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "timezest-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "timezest-mcp@latest"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

⏰ TimeZest MCP Server

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?

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

config.json

{
  "mcpServers": {
    "timezest": {
      "command": "npx",
      "args": ["-y", "timezest-mcp@latest"],
      "env": {
        "TIMEZEST_API_KEY": "your-timezest-api-key-here"
      }
    }
  }
}

Restart Claude Desktop. You're done.

Option 2: Claude Code CLI

Terminal

claude mcp add-json timezest-mcp '{
  "command": "npx",
  "args": ["-y", "timezest-mcp@latest"],
  "env": {
    "TIMEZEST_API_KEY": "your-timezest-api-key-here"
  }
}'

Option 3: VS Code (Copilot)

Add to your .vscode/settings.json or User Settings:

config.json

{
  "mcp": {
    "servers": {
      "timezest": {
        "command": "npx",
        "args": ["-y", "timezest-mcp@latest"],
        "env": {
          "TIMEZEST_API_KEY": "your-timezest-api-key-here"
        }
      }
    }
  }
}

🛠️ Available Tools

The server exposes 8 specialized tools that Claude can call:

Tool	Description	Key Parameters
`get_todays_appointments`	Morning briefing — today's confirmed appointments grouped by engineer, plus pending unbooked requests	`timezone`
`list_appointments`	Flexible query across any date range with optional filters	`start_date`, `end_date`, `engineer_name`, `status`
`get_engineer_schedule`	All upcoming appointments for a specific engineer, sorted by time	`engineer_name`, `days_ahead`, `include_pending`
`list_pending_requests`	Unbooked invitations (sent/new) with age tracking in hours/days	`days_back`, `engineer_name`, `older_than_hours`
`find_appointment_by_ticket`	Find appointments linked to a ConnectWise ticket number	`ticket_number` (e.g., `964400` or `#964400`)
`get_appointment_types`	List all appointment type definitions configured in TimeZest	—
`get_appointment_stats`	Aggregate summary: counts by status, by engineer, today's load, oldest pending	`days_back`, `days_forward`
`list_cancelled_appointments`	Cancelled requests with scheduling URLs for rebooking	`days_back`, `engineer_name`

💬 Example Prompts

Once connected, just talk to Claude naturally:

Code

"Who are my top engineers today and what are they booked for?"

"Find any TimeZest requests for ticket #964400."

"Give me a morning briefing of today's confirmed vs. unbooked requests."

"Show me all pending scheduling requests older than 48 hours."

"What's the scheduling volume breakdown for the last two weeks?"

"Pull up Sarah's schedule for the next 5 days."

"List all cancelled appointments from last week — any we should rebook?"

⚙️ Configuration

Environment Variable	Required	Default	Purpose
`TIMEZEST_API_KEY`	Yes	—	Your TimeZest Bearer token (Settings → API)
`TIMEZEST_DEFAULT_TZ`	No	`America/Chicago`	Default IANA timezone for localized display strings
`TIMEZEST_WINDOW_DAYS_BACK`	No	`14`	How many days back to fetch scheduling requests
`TIMEZEST_WINDOW_DAYS_FORWARD`	No	`30`	How many days forward to fetch scheduling requests

🏗️ Architecture

Code

┌─────────────────────────────────────────────────────────────────┐
│                        MCP CLIENT (Claude)                      │
│        Desktop App  •  Claude Code CLI  •  IDE Plugin           │
└──────────────────────────┬──────────────────────────────────────┘
                           │ Stdio (JSON-RPC)
┌──────────────────────────▼──────────────────────────────────────┐
│                     TIMEZEST MCP SERVER                         │
│                                                                 │
│  ┌──────────────┐  ┌──────────────┐                             │
│  │ Tool Handler │  │  MCP SDK     │  (index.ts)                 │
│  │ (8 Tools)    │  │  Registry    │                             │
│  └──────┬───────┘  └──────────────┘                             │
│         │                                                       │
│  ┌──────▼────────────────────────────────────────────────────┐  │
│  │                 TIMEZEST API CLIENT                        │  │
│  │  Pagination • Retry Logic • Rate Limit Management         │  │
│  └──────────────────────┬────────────────────────────────────┘  │
│                         │ (client.ts)                            │
│  ┌──────────────────────▼────────────────────────────────────┐  │
│  │               DATA TRANSFORMATION LAYER                    │  │
│  │  Timezone Math • Engineer Mapping • Ticket Linking         │  │
│  └────────────────────────────────────────────────────────────┘  │
│                         │ (utils/)                               │
└─────────────────────────┼────────────────────────────────────────┘
                          │ HTTPS / REST
┌─────────────────────────▼──────────────────────────────────────┐
│                      TIMEZEST API (v1)                          │
│       Scheduling Requests • Appointment Types • Resources       │
└─────────────────────────────────────────────────────────────────┘

Key Design Decisions

Read-Only: Intentionally kept read-only — no mutations to your scheduling data
Resilient Client: Exponential backoff with automatic Retry-After header 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_agents first, then falls back to resources
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:

Test File	Tests	Coverage
`transform.test.ts`	8	Engineer resolution, ticket extraction, timezone conversion, graceful handling of missing fields
`filter.test.ts`	6	Case-insensitive partial matching, team name matching, date-range filtering
`client.test.ts`	8	Appointment type caching, pagination, retry on 429/5xx, no-retry on 4xx

All tests use mocked API responses — no live API calls, no secrets needed.

Terminal

npm test            # Single run
npm run test:watch  # Re-runs on file save

🔒 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

Channel	Link
NPM	`timezest-mcp`
MCP Registry	`io.github.sagarkalra-tech/timezest-mcp`
GitHub	`sagarkalra-tech/TimeZest-MCP`

🤝 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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

192

Package downloads in the last 30 days.

Last commit

5mo ago

Most recent push to the default branch.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Timezest MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "timezest-mcp": { "command": "npx", "args": ["-y", "timezest-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/timezest-mcp?style=directory)](https://allmcps.com/mcp/timezest-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/timezest-mcp"><img src="https://allmcps.com/api/badge/timezest-mcp?style=directory" alt="Timezest MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

40Quality signal: Fair · 40/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools16/30

Adoption & activity4/15

Community engagement0/10

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Timezest MCP →Install in Claude Desktop Install in Cursor Install in VS Code