Back to MCP Servers
🔌

takumi0706/google-calendar-mcp

MITAPI key required

📇 ☁️ - An MCP server to interface with the Google Calendar API. Based on TypeScript.

TypeScriptCommunication

Install

npx -y @takumi0706/google-calendar-mcp@1.0.7

Required environment variables

GOOGLE_CLIENT_SECRETSet in your MCP config
TOKEN_ENCRYPTION_KEYSet in your MCP config

claude_desktop_config.json

claude_desktop_config.json
{
  "mcpServers": {
    "takumi0706-google-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@takumi0706/google-calendar-mcp@1.0.7"
      ],
      "env": {
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "TOKEN_ENCRYPTION_KEY": "<YOUR_TOKEN_ENCRYPTION_KEY>"
      }
    }
  }
}

Add this to your Claude Desktop config file. Find it at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.

What this does

takumi0706/google-calendar-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation. That makes it useful when you want Claude to reach into your team's communication channels without copy-pasting context every turn.

Requirements

This server needs the following environment variables to be set before it can run:

GOOGLE_CLIENT_SECRET
TOKEN_ENCRYPTION_KEY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Common use cases

  • Read recent threads, channels, or DMs to summarize team activity
  • Send messages, replies, or status updates as part of a workflow
  • Bring stakeholder context into a Claude conversation without copy-paste