Skip to main content
Glama
jaydenk

Fantastical MCP

by jaydenk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Fantastical MCP

No user-submitted related servers found.

    Related Servers

    • fantastical

      ramm
      A
      license
      A
      quality
      D
      maintenance
      Enables querying and managing Fantastical calendars and events via the MCP protocol, allowing AI assistants to list calendars, create events using natural language, and search or retrieve event details.
      6
      5
      MIT

    • Nico Apple MCP

      proxynico
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with local Apple Calendar, Notes, and Contacts on macOS. Provides tools for creating, reading, updating, and deleting events, notes, and contacts through natural language.
      MIT

    • macos-mcp

      krmj22
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, create, update, and delete data in macOS apps (Reminders, Calendar, Notes, Mail, Messages, Contacts) via natural language, using EventKit, JXA, and SQLite backends.
      36 npm
      8
      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

    A3.7/5.0

    Scored across 16 tools

    Disambiguation4/5

    Tools are largely distinct, but some overlap exists between get_today, get_upcoming, get_events_in_range, and get_recent, which all retrieve events over different time windows. Descriptions help distinguish them, but an agent might occasionally select the wrong one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_event, get_calendars, search_events). The pattern is predictable and easy to understand.

    Tool Count4/5

    16 tools is slightly on the high side for a calendar server, but each tool addresses a specific query need (today, upcoming, range, recurring, etc.). The JSON variants could be merged, but overall the count is still reasonable.

    Completeness2/5

    The tool surface is heavily read-oriented. While create_event is present, there are no tools for updating or deleting events, nor for responding to invitations. This leaves significant gaps in event lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources