Google Calendar MCP Server

Created By
ymelloa year ago
Overview

What is Google Calendar MCP Server?

Google Calendar MCP Server is an implementation of the Model Context Protocol (MCP) for Google Calendar that allows interaction with calendar events through CLI or Server-Sent Events (SSE).

How to use Google Calendar MCP Server?

To use the server, set up your environment with the required credentials, install dependencies, and run the server either as an HTTP/SSE server or as a CLI tool.

Key features of Google Calendar MCP Server?

  • List calendar events
  • Create new events
  • Update existing events
  • Delete events
  • Find available time slots

Use cases of Google Calendar MCP Server?

  1. Managing personal or team calendar events.
  2. Integrating with other applications that require calendar functionalities.
  3. Automating event management tasks through scripts.

FAQ from Google Calendar MCP Server?

  • What are the prerequisites to use this server?

You need Node.js 18 or higher, a Google account with access to the Google Calendar API, and OAuth 2.0 credentials from Google Cloud Console.

  • Can I run this server on any port?

Yes, you can specify a different port in the configuration.

  • Is there a way to troubleshoot common issues?

Yes, the documentation includes a troubleshooting section for common problems like authentication errors and server startup issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ymello
Star
0
Language
TypeScript
License
MIT 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