Google Calendar

Created By
takumi0706a year ago
Overview

what is Google Calendar MCP?

Google Calendar MCP is a Model Context Protocol (MCP) server implementation that integrates Google Calendar with Claude Desktop, allowing users to manage their calendar events seamlessly.

how to use Google Calendar MCP?

To use Google Calendar MCP, you need to create a Google Cloud Project, enable the Google Calendar API, configure OAuth2 credentials, and set up the server using the provided command.

key features of Google Calendar MCP?

  • Manage Google Calendar events (get, create, update, delete)
  • OAuth2 authentication with Google Calendar API
  • Integration with Claude Desktop via MCP SDK
  • Automatic browser opening for authorization
  • In-memory token management for enhanced security

use cases of Google Calendar MCP?

  1. Automating event creation and updates in Google Calendar.
  2. Integrating calendar functionalities into desktop applications.
  3. Streamlining event management for users of Claude Desktop.

FAQ from Google Calendar MCP?

  • How do I set up Google Calendar MCP?

Follow the installation instructions to create a Google Cloud Project, configure OAuth2 credentials, and run the server.

  • Is there any data stored on disk?

No, the server uses in-memory token management, ensuring that sensitive data is not stored on disk.

  • What should I do if I encounter errors?

Check the logs in your home directory and ensure your OAuth credentials are correctly configured.

Server Config

{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@takumi0706/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your_client_id",
        "GOOGLE_CLIENT_SECRET": "your_client_secret",
        "GOOGLE_REDIRECT_URI": "http://localhost:3000/oauth2callback"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
takumi0706
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago