Google Calendar

Created By
Jackson88a year ago
Overview

What is Google Calendar MCP?

Google Calendar MCP is a TypeScript-based Model Context Protocol (MCP) server that enables Claude Desktop to connect and interact with Google Calendar, allowing users to manage their calendar events seamlessly.

How to use Google Calendar MCP?

To use Google Calendar MCP, clone the repository from GitHub, install the necessary dependencies, configure your environment variables, and run the server. You can then connect Claude Desktop to the MCP server to manage your calendar events.

Key features of Google Calendar MCP?

  • Connects Claude Desktop AI to Google Calendar data.
  • Supports Google OAuth2 for secure authorization.
  • Allows retrieval, creation, updating, and deletion of calendar events.
  • Provides upcoming events across all calendars.
  • Strong typing with TypeScript for better development experience.

Use cases of Google Calendar MCP?

  1. Automating event scheduling through AI.
  2. Managing personal and professional calendar events.
  3. Integrating calendar functionalities into applications using Claude Desktop.

FAQ from Google Calendar MCP?

  • What is the recommended authentication method?

The recommended method is Google Cloud OAuth for better security and user experience.

  • Can I use this server without Google Cloud setup?

Yes, you can use direct authentication for personal or development purposes, but it has limitations.

  • What are the prerequisites for running the server?

You need Node.js (v16 or higher), npm or yarn, and a Google account with Calendar access.

Server Config

{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<your-client-id>",
        "GOOGLE_CLIENT_SECRET": "<your-client-secret>",
        "GOOGLE_REDIRECT_URI": "http://localhost:3000/auth/callback"
      },
      "description": "Google Calendar MCP server using npx"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Jackson88
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago