Google Calendar MCP Server

Created By
highlight-inga year ago
Overview

What is Google Calendar MCP Server?

Google Calendar MCP Server is a Model Context Protocol (MCP) server that provides tools for interacting with the Google Calendar API, allowing users to manage their calendar events programmatically.

How to use Google Calendar MCP Server?

To use the server, clone the repository, install the necessary dependencies, set up OAuth credentials in the Google Cloud Console, and configure the MCP settings to connect to the Google Calendar API.

Key features of Google Calendar MCP Server?

  • List upcoming calendar events with date range filtering
  • Create new calendar events with attendees
  • Update existing calendar events
  • Delete calendar events

Use cases of Google Calendar MCP Server?

  1. Automating event management for teams
  2. Integrating calendar functionalities into applications
  3. Programmatically managing personal calendar events

FAQ from Google Calendar MCP Server?

  • What are the prerequisites to use this server?

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

  • Is there a license for this project?

Yes, the project is licensed under the MIT license.

  • Can I use this server for personal projects?

Yes, you can use it for both personal and commercial projects as long as you comply with the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
highlight-ing
Star
0
Language
TypeScript
License
MIT license
Tags

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)

2 days ago