Skip to main content
Glama
UtahREIA

addevent-mcp-server

by UtahREIA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to addevent-mcp-server

No user-submitted related servers found.

    Related Servers

    • google-calendar-mcp

      wanthigh
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for Google Calendar integration with Claude Desktop. Create, update, delete, and manage calendar events with batch operations and enterprise-grade retry mechanisms.
      1
      MIT

    • booking_chest

      dsddet
      F
      license
      B
      quality
      D
      maintenance
      MCP server for Cal.com scheduling, providing ~70 tools to manage schedules, event types, bookings, calendars, webhooks, and teams. Enables natural language control of Cal.com from Claude or any MCP-compatible client.
      68
      -

    • caldav-mcp

      friisconsult
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server enables Claude to read and manage self-hosted CalDAV calendars (SOGo, Nextcloud, Radicale, etc.) with strict safety guardrails: read-only by default, optional writes only when explicitly enabled, no permanent deletes, and no event invitations.
      MIT

    • Google Calendar MCP Server

      Lokesh0252
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that allows Claude and other MCP clients to interact with Google Calendar. This server enables AI assistants to manage your calendar events, check availability, and handle scheduling tasks.
      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.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (create/search/get/update/delete for events, calendars, and RSVPs, plus list_timezones). The descriptions include explicit 'Don't use when' guidance to further prevent confusion between similar tools like search_events and get_event.

    Naming Consistency5/5

    All 16 tools follow the exact pattern `addevent_<verb>_<resource>` with verbs restricted to create, search, get, update, delete, and list. This uniform convention makes the tool's purpose immediately predictable from its name.

    Tool Count4/5

    16 tools is at the upper boundary of typical well-scoped server size, but each tool serves a clear CRUD need for one of three related resources (events, calendars, RSVPs) plus a single timezone lookup helper. Given the three independent resource lifecycles, this count is justified and not bloated.

    Completeness5/5

    The tool set provides full create, read/search, update, and delete coverage for events, calendars, and RSVPs, with no obvious dead ends. The timezone listing tool fills the only metadata gap needed to correctly create events and calendars, making the surface complete for its domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources