kronos-mcp
Related Servers
Alternatives to kronos-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI agents to manage spa/wellness operations via Zenoti API, including appointments, guests, services, and billing.42351 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to look up businesses, find free appointment slots, book, list and cancel appointments at salons, barbershops, nail and brow studios and clinics. Works read-only without a customer login by returning a pre-filled booking link, and can also run against a built-in demo with sample businesses.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing cron jobs, maintenance windows, and settings through natural language by exposing the Cronmanager REST API as MCP tools for LLM clients like Claude.GPL 3.0

Kalendis MCPofficial
AlicenseBqualityDmaintenanceEnables interaction with the Kalendis scheduling API to manage users, availability, bookings, and generate TypeScript clients and API routes. Supports comprehensive scheduling operations including recurring availability, exceptions, and booking management through natural language.4851 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.11 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover bookable time slots, book and cancel meetings, list events, and enable or disable scheduling links. Also supports managing webhooks and exposes write/destructive operations with MCP annotations so clients can confirm before acting.333 npmMIT
TDQS
Scored across 13 tools
The three slot-related tools have overlapping surface, but each is explicitly documented for a distinct scenario: full schedule, client-facing free slots, and resource-type-agnostic slots. All other tools target clearly separate resources/actions, so an agent can reliably differentiate with the descriptions.
All tools share the kronos_ prefix and use snake_case, but retrieval verbs are inconsistent: list_resources/list_services/list_events vs get_event/get_time_slots/get_available_slots/get_custom_fields. This is a minor deviation; the pattern is still mostly predictable.
13 tools is well-scoped for a booking/event management API: lookup, availability, CRUD, webhooks, custom fields, and CRM integration are each represented. No tool feels redundant, and the count is reasonable for the domain.
Event lifecycle is well covered with create, get, list, update, and delete, plus availability, services, resources, webhooks, and lead binding. A minor gap is the lack of an explicit resource-type listing tool and limited webhook management, but these are workable with existing tools.