From gcal-plugin
Guides setup of gcallm CLI for Google Calendar: installs via uv/pip, configures OAuth2 credentials from Google Cloud, and adds MCP server to Claude Code.
How this command is triggered — by the user, by Claude, or both
Slash command
/gcal-plugin:setupFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Google Calendar CLI Setup This command guides you through setting up the `gcallm` CLI for adding events to Google Calendar. ## Prerequisites You need: 1. OAuth2 credentials from Google Cloud Console 2. Google Calendar MCP server configured in Claude Code ## Step 1: Get OAuth2 Credentials 1. Go to [Google Cloud Console](https://console.cloud.google.com/apis/credentials) 2. Create a new project or select an existing one 3. Enable the **Google Calendar API**: - Go to "APIs & Services" > "Enable APIs and Services" - Search for "Google Calendar API" and enable it 4. Create OAuth2 cr...
This command guides you through setting up the gcallm CLI for adding events to Google Calendar.
You need:
~/gcp-oauth.keys.json)# Install from PyPI
uv tool install gcallm
# Or with pip
pip install gcallm
Verify installation:
which gcallm
# Should output: ~/.local/bin/gcallm (or similar)
Point gcallm to your OAuth credentials:
gcallm setup ~/gcp-oauth.keys.json
Or interactively:
gcallm setup
# Will prompt for path
gcallm requires the Google Calendar MCP server. Add it to Claude Code:
claude mcp add gcal npx @anthropic/mcp-google-calendar -s local
This uses the OAuth credentials you configured.
gcallm verify
Expected output:
Google Calendar MCP: OK
OAuth credentials: Configured
Test with a simple query:
gcallm ask "What's on my calendar today?"
~/.config/gcallm/
├── config.json # Settings (model, prompt)
└── oauth_path # Path to OAuth credentials
# OAuth credentials (shared with other Google tools)
~/gcp-oauth.keys.json # Or wherever you saved it
The Google Calendar MCP server isn't set up:
# Add the MCP server
claude mcp add gcal npx @anthropic/mcp-google-calendar -s local
# Verify it's configured
claude mcp list
Re-run setup with the correct path:
gcallm setup /correct/path/to/oauth-keys.json
Your OAuth token may have expired. Re-authenticate:
rm ~/.config/gcallm/*gcallm setup ~/gcp-oauth.keys.jsonEnsure the OAuth app has calendar scope:
https://www.googleapis.com/auth/calendar/gcal - Usage guide for gcallm CLInpx claudepluginhub warrenzhu050413/warren-claude-code-plugin-marketplace --plugin gcal-plugin/gws-installInstalls Google Workspace CLI (gws) on the current machine using existing OAuth credentials from a previous setup.
/setupConfigures GCloud CLI authentication: checks installation, installs if needed via brew/curl/download, authenticates user and ADC, sets default project, verifies setup for MCP.
/setupSets up connect-apps plugin: prompts for Composio API key, validates it via Python/Bash, writes MCP config to ~/.mcp.json enabling actions in 500+ apps like Gmail, Slack, GitHub.
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.