Skip to main content
Glama
watanka

Schedulia MCP

by watanka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Schedulia MCP

No user-submitted related servers found.

    Related Servers

    • MCP Outlook Scheduler

      ChitSingh
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to intelligently schedule meetings by checking Microsoft Outlook calendars, finding available time slots across multiple participants, and automatically booking meetings with Teams integration. Uses Microsoft Graph API with smart fallback logic for optimal scheduling.
      1
      -

    • @astrocal/mcp-server

      astrocal-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to schedule meetings via Astrocal's scheduling API, including checking availability, booking, canceling, rescheduling, and managing waitlists through natural conversation.
      62 npm
      1
      MIT

    • mcp-meetsync

      nicholasemccormick
      A
      license
      A
      quality
      D
      maintenance
      Integrates the MeetSync calendar negotiation API to enable AI agents to autonomously manage participants, find mutual availability, and handle meeting bookings. It exposes 19 tools for end-to-end scheduling workflows including participant preferences, proposals, and confirmations.
      19
      4 npm
      MIT

    • MCP Calendar Assistant

      momer17
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage calendars and tasks through natural language, supporting Google Calendar operations like event creation, availability checking, and smart scheduling. It features schedule analysis, task reminders, and meeting time recommendations to streamline productivity.
      -
    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

    C2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: requesting meetings, responding to requests, viewing requests, and viewing schedules. The actions (request, respond, view) and targets (meeting_requests, meeting_schedules) are well-defined, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., request_meeting, respond_to_meeting_request). The naming is predictable and readable throughout the set, with no deviations in style or convention.

    Tool Count4/5

    With 4 tools, the count is reasonable for a scheduling/meeting domain, covering core actions like request, respond, and view. It might be slightly thin if advanced features (e.g., cancel_meeting, update_schedule) are expected, but it's well-scoped for basic functionality.

    Completeness3/5

    The tools cover key aspects of meeting management (requesting, responding, viewing), but there are notable gaps. For example, there's no tool to cancel or modify meetings, and no direct scheduling creation tool, which could limit agent workflows in a full meeting lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources