Google Calendar MCP Server

Created By
KhryptorGraphicsa year ago
MCP server for Google Calendar integration
Overview

What is Google Calendar MCP Server?

Google Calendar MCP Server is a server that provides integration with Google Calendar, allowing users to view, create, and manage calendar events through a standardized interface.

How to use Google Calendar MCP Server?

To use the server, set up a Google Cloud project with the Calendar API enabled, install the necessary dependencies, and authenticate using OAuth 2.0 credentials.

Key features of Google Calendar MCP Server?

  • List available calendars
  • List events from a calendar
  • Create new calendar events
  • Update existing events
  • Delete events

Use cases of Google Calendar MCP Server?

  1. Automating calendar event management for applications.
  2. Integrating calendar functionalities into chatbots or virtual assistants.
  3. Building custom applications that require calendar event handling.

FAQ from Google Calendar MCP Server?

  • What are the prerequisites to use this server?

You need Node.js 16 or higher and a Google Cloud project with the Calendar API enabled.

  • How do I authenticate with Google Calendar?

The server will start an authentication process that opens a browser for OAuth authentication and saves the tokens securely.

  • What happens if my OAuth token expires?

You will need to re-authenticate if the app is in testing mode.

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

2 days ago