Google Calendar MCP Server

Created By
highlight-inga year ago
Overview

What is Google Calendar MCP Server?

Google Calendar MCP Server is a Model Context Protocol (MCP) server that provides tools for interacting with the Google Calendar API, allowing users to manage their calendar events programmatically.

How to use Google Calendar MCP Server?

To use the server, clone the repository, install the necessary dependencies, set up OAuth credentials in the Google Cloud Console, and configure the MCP settings to connect to the Google Calendar API.

Key features of Google Calendar MCP Server?

  • List upcoming calendar events with date range filtering
  • Create new calendar events with attendees
  • Update existing calendar events
  • Delete calendar events

Use cases of Google Calendar MCP Server?

  1. Automating event management for teams
  2. Integrating calendar functionalities into applications
  3. Programmatically managing personal calendar events

FAQ from Google Calendar MCP Server?

  • What are the prerequisites to use this server?

You need Node.js version 14 or higher and a Google Cloud project with the Google Calendar API enabled.

  • Is there a license for this project?

Yes, the project is licensed under the MIT license.

  • Can I use this server for personal projects?

Yes, you can use it for both personal and commercial projects as long as you comply with the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
highlight-ing
Star
0
Language
TypeScript
License
MIT license
Tags

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