Skip to main content
Glama

Related Servers

Alternatives to kronos-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage appointments, reschedule bookings, look up clients, and add client notes in a user's signed-in business account without requiring an API key.
      7
      Elastic 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to work within a user's signed-in business account to read and change bookings and client lists, including booking, rescheduling, finding open slots, and following up with clients.
      7
      24 PyPI
      Elastic 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read agents, teams, appointment types, bookable resources, and scheduling requests from the TimeZest API, and to create a scheduling request when explicitly requested, optionally linked to a PSA ticket. This supports appointment-booking workflows where MSP customers book time with technicians from PSA tickets.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.