google-calendar-mcp-python

Created By
Anderson-Lee-Gita year ago
A python-based MCP server for google calendar
Overview

what is google-calendar-mcp-python?

google-calendar-mcp-python is a Python-based MCP (Multi-Channel Protocol) server designed to interact with Google Calendar, allowing users to manage their calendar events programmatically.

how to use google-calendar-mcp-python?

To use this project, clone the repository from GitHub, install the required dependencies, and run the server. You can then send requests to the server to create, read, update, or delete calendar events.

key features of google-calendar-mcp-python?

  • Programmatic access to Google Calendar events
  • Support for creating, updating, and deleting events
  • Easy integration with other applications via API calls

use cases of google-calendar-mcp-python?

  1. Automating event creation for a scheduling application.
  2. Syncing calendar events with other platforms.
  3. Building custom notifications for calendar events.

FAQ from google-calendar-mcp-python?

  • Is this project officially supported by Google?

No, this is an independent project and is not officially supported by Google.

  • What are the prerequisites for using this project?

You need to have Python installed and access to the Google Calendar API.

  • Can I contribute to this project?

Yes! Contributions are welcome. Please check the GitHub repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Anderson-Lee-Git
Star
0
Language
-
License
-

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.

3 hours ago
Gpt Scrambler

2 days ago