Google Calendar MCP Server

Created By
masa1023a year ago
Overview

what is Google Calendar MCP Server?

Google Calendar MCP Server is a Model Context Protocol (MCP) server that provides access to Google Calendar data, allowing users to interact with their calendars programmatically.

how to use Google Calendar MCP Server?

To use the server, set up your Google Cloud project with Calendar API enabled, install the required dependencies, configure your OAuth2 credentials, and run the server using Python.

key features of Google Calendar MCP Server?

  • List available Google Calendars
  • Find available time slots in a calendar
  • Get upcoming events from a calendar

use cases of Google Calendar MCP Server?

  1. Integrating Google Calendar functionalities into applications.
  2. Automating scheduling tasks based on calendar availability.
  3. Fetching and displaying upcoming events in custom interfaces.

FAQ from Google Calendar MCP Server?

  • What are the prerequisites to run the server?

You need Python 3.9+, a Google Cloud project with Calendar API enabled, and OAuth2 credentials.

  • How do I install the server dependencies?

Use the command pip install -r requirements.txt to install the necessary packages.

  • Can I customize the time slot duration?

Yes, you can specify the slot_duration_minutes parameter when finding available slots.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
masa1023
Star
0
Language
Python
License
-

Recommend Servers

View All
Alloy

2 days 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)

8 hours ago
Crevio

a day ago