Skip to main content
Glama
Sign In
icskit-mcp

icskit-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to icskit-mcp

No user-submitted related servers found.

    Related Servers

    • Calendar MCP Server

      0xmortuex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to inspect and safely edit local .ics calendar files, query agendas, find free/busy slots, detect overlaps, and handle time zones, DST, and recurrence rules.
      MIT

    • iCal MCP Server

      jnss95
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to load, query, and manage iCalendar files with full CRUD operations and support for multiple calendars.
      8
      9 npm
      MIT

    • MCP Calendar Tools

      Preeti325
      F
      license
      B
      quality
      D
      maintenance
      Enables reading and managing calendar events from local .ics files offline, without OAuth.
      2
      -

    • caldav-mcp

      gelse
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI assistants read/write access to any CalDAV calendar, enabling natural language management of events, attendees, and calendar queries across Nextcloud, Radicale, iCloud, and more.
      6
      MIT

    • Apple Calendar MCP

      OwenSuyko
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server for macOS that enables AI assistants to read and manage Apple Calendar events via EventKit, with configurable permissions, audit logging, and a native setup app.
      MIT
    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

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    The three read tools (agenda, next_occurrences, search_events) overlap somewhat since all can expand recurring events over a range, but the descriptions draw clear boundaries: agenda is a range dump, next_occurrences targets one UID, search_events filters by text/attendee/location. The remaining tools (find_free_time, find_conflicts, export_agenda_markdown, create/update/delete_event, calendar_overview) each have an unmistakable purpose.

    Naming Consistency4/5

    All names are snake_case and readable, with mutations consistently using verb_noun (create_event, update_event, delete_event) and searches using verb_noun (search_events, find_free_time, find_conflicts). The read tools agenda, calendar_overview and next_occurrences break the pattern by being noun- or prefix-style, but the convention still reads predictably.

    Tool Count5/5

    Ten tools is a well-scoped surface for an iCalendar server: six query/analysis tools, one export, and exactly the three mutation tools needed. Nothing feels redundant or padded.

    Completeness4/5

    Full lifecycle is covered: discovery (calendar_overview), range/text lookup, free-busy and conflict analysis, export, plus create/update/delete with series-level EXDATE handling. Gaps remain: no way to read a single event's full record by UID, no per-instance modification of a series, and no tool to move/copy events between calendar files.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources