Calendar MCP Server

Created By
smithery-aia year ago
Overview

what is Calendar MCP Server?

Calendar MCP Server is a Model Context Protocol (MCP) server designed for integrating Google Calendar with AI assistants, enabling users to manage their calendar events through natural language interactions.

how to use Calendar MCP Server?

To use the Calendar MCP Server, you can install it via Smithery or manually via npm, and then set it up by creating a Google Cloud Project and configuring your OAuth credentials.

key features of Calendar MCP Server?

  • Create, update, delete, and list calendar events
  • Retrieve event details by event ID
  • Full integration with Google Calendar API
  • Secure OAuth2 authentication

use cases of Calendar MCP Server?

  1. Automating event creation and management via AI-powered commands
  2. Integrating calendar functionalities into AI assistants like Claude Desktop
  3. Allowing users to interact with Google Calendar through natural language processing

FAQ from Calendar MCP Server?

  • Is the Calendar MCP Server free to use?

Yes! The Calendar MCP Server is open-source and free to use.

  • What are the security measures when using this server?

Users should keep their Google API credentials secure, regularly rotate refresh tokens, and never share their credentials publicly.

  • Can I contribute to the Calendar MCP Server?

Yes! Contributions are welcome, and you can submit a pull request on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
smithery-ai
Star
-
Language
-
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.

31 minutes ago