Google Calendar MCP Server

Created By
surana-mudita year ago
MCP server for google calendar
Overview

What is Google Calendar MCP Server?

Google Calendar MCP Server is a server that provides access to Google Calendar events, allowing users to manage their calendar through an MCP interface. It is compatible with Claude Desktop and other MCP-compatible clients.

How to use Google Calendar MCP Server?

To use the server, clone the repository, set up a Python virtual environment, install dependencies, and configure Google Calendar API credentials. Then, integrate it with Claude Desktop or Cursor for managing calendar events.

Key features of Google Calendar MCP Server?

  • View calendar events for any date or date range.
  • Create new events with details like title, time, description, location, and attendees.
  • Update existing events with new information.
  • Pre-built prompts for common calendar actions.

Use cases of Google Calendar MCP Server?

  1. Managing personal calendar events through voice commands.
  2. Scheduling meetings and appointments easily.
  3. Integrating calendar management into applications using MCP.

FAQ from Google Calendar MCP Server?

  • What are the requirements to run the server?

You need Python 3.10 or higher, a Google Cloud project with Calendar API enabled, and OAuth credentials for authentication.

  • Is there a way to troubleshoot issues?

Yes! Common issues include Python version problems and authentication errors, which can be resolved by checking your setup and ensuring correct permissions for your credentials file.

  • Can I use this server with other applications?

Yes! The server can be integrated with any MCP-compatible client, allowing for flexible usage.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
surana-mudit
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Gpt Scrambler

2 days 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