Google Calendar MCP Server

Created By
rsc1102a year ago
Model Context Protocol (MCP) server that integrates with the Google Calendar API
Overview

What is Google Calendar MCP?

Google Calendar MCP is a Model Context Protocol (MCP) server that integrates with the Google Calendar API, allowing users to manage their calendar events seamlessly.

How to use Google Calendar MCP?

To use Google Calendar MCP, you need to install the server, set up Google Cloud credentials, and integrate it with Anthropic's Claude Desktop. Once configured, you can interact with your Google Calendar through Claude.

Key features of Google Calendar MCP?

  • List, create, delete, and update calendar events.
  • Seamless integration with Claude Desktop via MCP.

Use cases of Google Calendar MCP?

  1. Managing personal calendar events through voice commands.
  2. Automating event scheduling and reminders.
  3. Integrating calendar management into applications using Claude.

FAQ from Google Calendar MCP?

  • Do I need a Google account to use this?

Yes, a Google account is required to access the Google Calendar API.

  • Is there a cost associated with using Google Calendar MCP?

The server itself is free to use, but standard Google API usage policies apply.

  • Can I use this with other applications?

Yes, as long as they support the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rsc1102
Star
2
Language
Python
License
-

Recommend Servers

View All
Voyei

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

a day ago