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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago