MCP Google Calendar Server

Created By
iamaparka year ago
Overview

What is MCP Google Calendar Server?

MCP Google Calendar Server is an integration server based on the Model Context Protocol (MCP) that allows clients like Claude Desktop to add events to Google Calendar.

How to use MCP Google Calendar Server?

To use the server, clone the repository, install dependencies, set up environment variables, and configure it with Claude Desktop.

Key features of MCP Google Calendar Server?

  • Google OAuth 2.0 authentication
  • Add events to Google Calendar
  • Retrieve events from Google Calendar (supports period-based queries)
  • Fetch today's date
  • Support for Korean Standard Time (KST)
  • Detailed error handling and logging

Use cases of MCP Google Calendar Server?

  1. Integrating Google Calendar with desktop applications.
  2. Automating event creation and retrieval for personal or business use.
  3. Enhancing productivity tools with calendar functionalities.

FAQ from MCP Google Calendar Server?

  • Is the server free to use?

Yes! The MCP Google Calendar Server is free to use.

  • What programming language is used?

The server is built using TypeScript.

  • How do I handle errors?

The server provides detailed error messages for various scenarios, including authentication issues and incorrect input formats.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iamapark
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)

11 hours ago