Google Calendar MCP Server with Service Account authentication
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"youyo-google-calendar-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Google Calendar MCP Google Calendar MCP is a Model Context Protocol (MCP) server implementation in Python with Service Account authentication. [日本語 README はこちら](README_ja.md) ## Overview This project implements the Google Calendar API as an MCP server in Python. It is a port from the original TypeScript version, with authentication changed from OAuth 2.0 to Service Account. ## Features - Python 3.13 support - MCP (Model Context Protocol) server implementation - Google Calendar API integration - Service Account authentication - Dependency management with uv ## Requirements - Python 3.13 or higher - A Google Cloud Platform project and a valid Service Account - The Service Account must have access to the Google Calendar API ## Installation ```bash # Clone the repository git clone https://github.com/youyo/google-calendar-mcp.git cd google-calendar-mcp # Install dependencies uv pip install -r requirements.txt ``` ## Configuration 1. Create a project in Google Cloud Platform and enable the Google Calendar API. 2. Create a Service Account and download the JSON key file. 3. Set the environment variable `GOOGLE_APPLICATION_CREDENTIALS` to the path of the JSON key file. ```bash export GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json ``` Optionally, you can set the default calendar ID via the environment variable: ```bash export GOOGLE_CALENDAR_ID=your-calendar-id@example.com ``` If not specified in arguments, this value will be used as the default calendarId. ### Example: MCP configuration file To use this server with an MCP client, add the following to your MCP configuration file. Set both `GOOGLE_APPLICATION_CREDENTIALS` and `GOOGLE_CALENDAR_ID` in the `env` section to specify authentication and the default calendar: ```json { "mcpServers": { "google-calendar-mcp": { "command": "uvx", "args": ["google-calendar-mcp@latest"], "env": { "GOOGLE_APPLICATION_CREDENTIALS": "/path/to/service-account.json", "…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.