MCP Google Calendar

Created By
takumi0706a year ago
A Model Context Protocol (MCP) server for Google Calendar integration with Claude and other AI assistants.
Overview

What is MCP Google Calendar?

MCP Google Calendar is a Model Context Protocol (MCP) server that enables integration with Google Calendar, allowing AI assistants like Claude to manage calendar events through natural language.

How to use MCP Google Calendar?

To use MCP Google Calendar, install it via npm, configure your Google API credentials, and run the server. You can then interact with it through an AI assistant by issuing commands related to your calendar.

Key features of MCP Google Calendar?

  • View, create, update, and delete calendar events
  • Search for events by time range, keywords, or participants
  • Get free/busy times for scheduling
  • List available calendars
  • Set up meeting invitations with attendees

Use cases of MCP Google Calendar?

  1. Scheduling meetings with colleagues using natural language.
  2. Checking availability for events and finding free time slots.
  3. Managing personal and work calendars seamlessly through AI.

FAQ from MCP Google Calendar?

  • Can I use MCP Google Calendar with any AI assistant?
    Yes! It is designed to work with AI assistants like Claude.

  • Is there a cost to use MCP Google Calendar?
    No, it is free to use.

  • What do I need to set it up?
    You need a Google account, access to the Google Calendar API, and to follow the setup instructions provided in the documentation.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

16 hours ago
Voyei

6 hours ago