A
licenseNot graded
qualityC
maintenanceExposes the Appointment Scheduler API to AI agents as an MCP server, enabling them to list users and services, check availability, book, list, and cancel appointments via natural language.
Apache 2.0
timezest-mcp
by WYRE-AI
Related Servers
Alternatives to timezest-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that wraps the TimePRO API, enabling AI assistants to automatically create, view, and manage timesheets for authenticated users. It provides tools for searching clients and projects, retrieving configuration defaults, and performing full CRUD operations on timesheet entries.10-
- AlicenseAqualityDmaintenanceMCP server that connects AI agents to calendars, bookings, and scheduling polls via the Model Context Protocol.227 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that exposes the Orita scheduling API as tools for AI agents, enabling them to look up event types, book appointments, and manage bookings.47 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with OnSched's consumer-facing appointment scheduling API through natural language, allowing users to manage bookings, appointments, and scheduling operations.-
- FlicenseAqualityDmaintenanceAn MCP server that enables scheduling, updating, deleting, and listing calendar appointments through Cal.com's Calendar API.43-
TDQS
B3.3/5.0
Scored across 12 tools
Disambiguation4/5
Most tools are clearly separated by resource and action, such as agents_list vs agents_get and scheduling_list vs scheduling_get. The only potential confusion is resources_list, which overlaps with agents_list and teams_list, though it is clearly described as an aggregate.
Naming Consistency4/5
All tools share the timezest_ prefix and mostly follow a resource_action pattern, e.g., agents_list, teams_get, scheduling_cancel. The exceptions are timezest_status, which doesn't follow the pattern, and scheduling_create_request, where the action is verbose rather than just create.
Tool Count5/5
Twelve tools is a reasonable, well-scoped count for a scheduling MCP server. Each resource area has list/get coverage and scheduling requests have create, list, get, and cancel operations.
Completeness4/5
The core scheduling workflow is covered: creating, listing, retrieving, and canceling requests, plus lookup of agents, teams, appointment types, and resources. Missing update/reschedule functionality is a minor gap, but agents can likely work around it by canceling and recreating.
Maintenance
ActivityActive
ResponsivenessNo issues