timezest-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | Set to 'gateway' for WYRE gateway integration | |
| LOG_LEVEL | No | Log level: debug, info (default), warn, error | info |
| MCP_HTTP_PORT | No | HTTP port (default: 8080) | 8080 |
| MCP_TRANSPORT | No | Transport mode: stdio (default) or http | stdio |
| TIMEZEST_API_TOKEN | Yes | TimeZest API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| timezest_statusA | Show TimeZest connection status and the available tools |
| timezest_agents_listB | List all agents (technicians) available for scheduling |
| timezest_agents_getA | Get details for a specific agent by ID |
| timezest_teams_listB | List teams available for scheduling. Deleted teams are omitted, using the same live set as timezest_resources_list (teams GET /v1/resources still returns). |
| timezest_teams_getA | Get details for a specific team by ID |
| timezest_appointment_types_listB | List all appointment types available for scheduling |
| timezest_appointment_types_getB | Get details for a specific appointment type by ID |
| timezest_resources_listC | List all resources (agents and teams) available for scheduling |
| timezest_scheduling_listC | List scheduling requests |
| timezest_scheduling_getA | Get details for a specific scheduling request by ID |
| timezest_scheduling_create_requestC | Create a new scheduling request - supports PSA ticket association |
| timezest_scheduling_cancelC | Cancel a scheduling request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| TimeZest Scheduling Request Card | Interactive MCP Apps card rendering a TimeZest scheduling request |
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action, with list/get pairs for agents, teams, appointment types, and scheduling requests. The main overlap is timezest_resources_list versus timezest_agents_list/timezest_teams_list, but the descriptions clarify that resources is the combined view.
Most tools follow the consistent pattern timezest_<resource>_<action>, using snake_case throughout. Minor inconsistencies exist, such as timezest_scheduling_create_request using a compound action while timezest_scheduling_cancel drops the '_request' suffix.
The 12 tools are well-scoped for a scheduling/fieldservice MCP server. Each tool covers a meaningful function without unnecessary duplication or bloat.
The tool set covers the core workflow: viewing status, reference data (agents, teams, resources, appointment types), listing/getting scheduling requests, and creating/canceling them. Minor gaps exist, such as no update/reschedule operation or agent availability check, but the main scheduling lifecycle is represented.