Skip to main content
Glama
highthon-16

MCP Calendar Server

by highthon-16

Related Servers

Alternatives to MCP Calendar Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Integrates simulated health data and task management to provide energy-aware scheduling based on calculated readiness scores. It allows users to query health summaries, manage tasks, and generate optimized daily schedules through a local SQLite database.
      5
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read, create, update, move, and delete calendar events, list calendars, and query free/busy across multiple independent Google accounts through a single interface, with each account routed explicitly and gated by role-based access control. It also includes a built-in personal time-management assistant and stores each account's OAuth tokens in a local encrypted vault.
      25
      97 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Integrates the YearAtAGlance calendar with AI assistants to manage events, categories, and event density heatmaps. It enables users to perform CRUD operations on calendar data and utilize AI-powered features like natural language milestone creation and yearly analysis.
      15
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to track daily calorie consumption by logging meals through natural language and searching a comprehensive food database. It provides daily summaries, weekly reports, and persistent SQLite storage to monitor dietary trends and goals.
      6 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. The CRUD operations (create, get, update, delete) target different actions, while the query tools (get_all_events, get_events_by_category, get_events_by_date) provide complementary filtering options. The complete_event tool uniquely handles event completion with stamina management, separate from general updates.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (create_calendar_event, delete_calendar_event, update_calendar_event, get_all_events, get_event_by_id, get_events_by_category, get_events_by_date). The only deviation is complete_event, which uses a different verb style and omits the 'calendar' prefix, but this is minor given its distinct functionality.

    Tool Count5/5

    With 8 tools, this server is well-scoped for calendar management. It provides full CRUD operations plus specialized queries and a unique completion tool, avoiding both under-coverage (e.g., just 1-2 tools) and bloat (e.g., 25+ tools). Each tool earns its place in the workflow.

    Completeness5/5

    The toolset offers complete coverage for calendar event management: create, read (with multiple query options), update, and delete operations. It also includes specialized functionality like event completion with stamina tracking and status management. No obvious gaps exist for the domain, supporting full agent workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues