Skip to main content
Glama
takumi0706

Google Calendar MCP Server

by takumi0706
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Google Calendar MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Google Calendar MCP Server

      pranavmanoj1
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables natural language interaction with Google Calendar, allowing users to view, create, update, and delete calendar events through context-aware operations.
      75 npm
      1
      MIT

    • 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

    • calendar-mcp

      deciduus
      A
      license
      A
      quality
      A
      maintenance
      This project implements a Python-based MCP (Model Context Protocol) server that acts as an interface between Large Language Models (LLMs) and the Google Calendar API. It enables LLMs to perform calendar operations via natural language requests.
      23
      101 PyPI
      26
      AGPL 3.0
    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 5 tools

    Disambiguation5/5

    Each tool targets a distinct action on calendar events—listing, creating, updating, deleting—plus a separate authentication flow. There is no overlap or ambiguity between the tools.

    Naming Consistency4/5

    Four tools follow a clear verb+Event pattern (getEvents, createEvent, updateEvent, deleteEvent), while authenticate is a necessary but non-parallel exception. Overall the naming is predictable and easy to infer.

    Tool Count5/5

    Five tools is a well-scoped set for a Google Calendar event server: authentication plus full CRUD operations. Each tool serves a clear purpose without unnecessary bloat.

    Completeness5/5

    The server covers the full event lifecycle—list, create, update, delete—and includes OAuth authentication as a prerequisite. There are no obvious dead ends or critical missing operations for managing calendar events.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources