Server data from the Official MCP Registry
MCP server for TimeZest — appointment scheduling, agents, appointment types, and resources for MSPs.
MCP server for TimeZest — appointment scheduling, agents, appointment types, and resources for MSPs.
This is a well-structured MCP server for TimeZest scheduling with proper authentication via API tokens, clean separation of concerns across domains, and appropriate permission scoping. The server requires TIMEZEST_API_TOKEN for operation, handles credentials via environment variables with gateway-mode support, and includes input validation and error handling. Minor code quality observations exist around broad exception catching, but these are typical for MCP servers and do not constitute security vulnerabilities. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 2 high severity).
7 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: TIMEZEST_API_TOKEN
Environment variable: MCP_TRANSPORT
Environment variable: AUTH_MODE
Environment variable: LOG_LEVEL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-wyre-technology-timezest-mcp": {
"env": {
"AUTH_MODE": "your-auth-mode-here",
"LOG_LEVEL": "your-log-level-here",
"MCP_TRANSPORT": "your-mcp-transport-here",
"TIMEZEST_API_TOKEN": "your-timezest-api-token-here"
},
"args": [
"-y",
"@wyre-technology/timezest-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP (Model Context Protocol) server for TimeZest scheduling platform. Enables LLM agents to create and manage technician scheduling requests with PSA integration.
docker run -it --rm \
-e TIMEZEST_API_TOKEN=your-api-token \
ghcr.io/wyre-technology/timezest-mcp:latest
npm install -g @wyre-technology/timezest-mcp
TIMEZEST_API_TOKEN=your-token timezest-mcp
| Environment Variable | Required | Description |
|---|---|---|
TIMEZEST_API_TOKEN | Yes | TimeZest API token |
MCP_TRANSPORT | No | Transport mode: stdio (default) or http |
MCP_HTTP_PORT | No | HTTP port (default: 8080) |
AUTH_MODE | No | Set to gateway for WYRE gateway integration |
LOG_LEVEL | No | Log level: debug, info (default), warn, error |
The server uses decision-tree navigation to organize tools by domain:
timezest_navigate - Enter a domain to access its toolstimezest_status - Show available domains and current statetimezest_agents_list - List individual technicianstimezest_agents_get - Get agent detailstimezest_teams_list - List teams (round-robin scheduling)timezest_teams_get - Get team detailstimezest_appointment_types_list - List available service typestimezest_appointment_types_get - Get appointment type detailstimezest_resources_list - List all resources (agents + teams)timezest_scheduling_list - List scheduling requeststimezest_scheduling_get - Get request detailstimezest_scheduling_create_request - Create new request (key tool)timezest_scheduling_cancel - Cancel requestUser: "Show me TimeZest domains"
Tools: timezest_status
User: "Go to scheduling"
Tools: timezest_navigate(domain="scheduling")
User: "Book a technician for server repair at Customer Corp tomorrow"
Tools: timezest_scheduling_create_request({
"appointmentTypeId": "repair-onsite",
"triggerMode": "pod",
"endUser": {
"name": "John Doe",
"company": "Customer Corp",
"email": "john@customer.com"
},
"timeRange": {
"earliestDate": "2024-02-01",
"earliestTime": "09:00",
"latestDate": "2024-02-01",
"latestTime": "17:00",
"timezone": "America/New_York"
},
"associatedEntities": [
{"type": "connectwise", "id": "12345", "number": "T20240001"}
]
})
Link scheduling requests to PSA tickets:
{
"associatedEntities": [
{"type": "connectwise", "id": "12345", "number": "T20240001"},
{"type": "autotask", "id": "67890"},
{"type": "halo", "id": "11111"}
]
}
pod: Fires the configured PSA workflow (creates calendar entries, updates tickets)generate_url: Returns a shareable booking URL for customersTimeZest Query Language examples:
# Active agents in IT department
filter: "active:true AND department:\"IT Support\""
# Recent scheduling requests
filter: "createdAt:>=2024-01-01 AND status:pending"
# Specific customer requests
filter: "endUser.company:\"Important Customer\""
CRITICAL: Always specify IANA timezones explicitly. TimeZest interprets scheduling windows in the specified timezone.
{
"timeRange": {
"earliestDate": "2024-02-01",
"earliestTime": "09:00",
"timezone": "America/New_York" // ✅ Required
}
}
# Clone and install
git clone https://github.com/wyre-technology/timezest-mcp.git
cd timezest-mcp
npm install
# Development with file dependency (replace before publish)
# Edit package.json: "@wyre-technology/node-timezest": "file:../node-timezest"
# Build and test
npm run build
npm test
# Run locally
TIMEZEST_API_TOKEN=your-token npm run dev
# Build image
docker build -t timezest-mcp --build-arg NODE_AUTH_TOKEN=$GITHUB_TOKEN .
# Run container
docker run -it --rm \
-e TIMEZEST_API_TOKEN=your-token \
-e LOG_LEVEL=debug \
timezest-mcp
Add to your MCP settings:
{
"mcpServers": {
"timezest": {
"command": "npx",
"args": ["@wyre-technology/timezest-mcp"],
"env": {
"TIMEZEST_API_TOKEN": "your-api-token"
}
}
}
}
The server is designed for the WYRE MCP Gateway with:
| TimeZest API | Coverage | Notes |
|---|---|---|
| Agents | ✅ List, Get | Individual technicians |
| Teams | ✅ List, Get | Round-robin scheduling |
| Appointment Types | ✅ List, Get | Service type definitions |
| Resources | ✅ List | Unified agents + teams |
| Scheduling Requests | ✅ CRUD | Core scheduling functionality |
| TQL Filtering | ✅ All endpoints | TimeZest Query Language |
| PSA Integration | ✅ All systems | ConnectWise, Autotask, Halo |
| Webhooks | ❌ N/A | TimeZest doesn't provide webhooks |
See CONTRIBUTING.md for development guidelines.
Apache 2.0 - see LICENSE file for details.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.