Skip to main content
Glama
WYRE-AI

timezest-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to timezest-mcp

No user-submitted related servers found.

    Related Servers

    • appointment-scheduler-mcp

      ProductDock
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes 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

    • TimePRO MCP Server

      calumjs
      A
      license
      A
      quality
      D
      maintenance
      An 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
      MIT

    • TimeZest MCP Server

      MSPbotsAIFramework
      A
      license
      Not graded
      quality
      B
      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

    • OnSched Consumer API MCP

      ag2-mcp-servers
      F
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    The 12 tools are well-scoped for a scheduling/fieldservice MCP server. Each tool covers a meaningful function without unnecessary duplication or bloat.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources