Google Calendar MCP Server

Created By
agc129a year ago
Overview

What is Google Calendar MCP Server?

Google Calendar MCP Server is a Model Context Protocol (MCP) server that integrates with Google Calendar, allowing LLM applications to manage calendar events through a standardized interface.

How to use Google Calendar MCP Server?

To use the server, set up the required environment variables in a .env file and run the server using the command uv run client.py after installation.

Key features of Google Calendar MCP Server?

  • List available calendars
  • List events from a calendar
  • Create new calendar events
  • Update existing events
  • Delete events

Use cases of Google Calendar MCP Server?

  1. Automating event management for applications using LLMs.
  2. Integrating calendar functionalities into chatbots or virtual assistants.
  3. Streamlining scheduling processes in software applications.

FAQ from Google Calendar MCP Server?

  • What is the purpose of this server?

It provides a standardized way for LLM applications to interact with Google Calendar events.

  • How do I set up the Google Calendar API?

Follow the setup instructions in the Google Cloud Console to enable the API and create OAuth 2.0 credentials.

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

The server itself is free to use, but Google Calendar API usage may incur costs based on your usage.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
agc129
Star
0
Language
Python
License
-

Recommend Servers

View All
Gpt Scrambler

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

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago