Skill

authenticate

Authenticate Gmail and Google Calendar MCP servers. Use after first install, after codespace rebuild, or when MCP authentication fails. Runs OAuth flow for both Gmail and Calendar services.

Install

npx claudepluginhub reggiechan74/cc-plugins --plugin google-workspace-mcp

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Authenticate the Gmail and Google Calendar MCP servers via OAuth 2.0.

SKILL.md

Similar Skills

cpp-coding-standards

Enforces C++ Core Guidelines for writing, reviewing, and refactoring modern C++ code (C++17+), promoting RAII, immutability, type safety, and idiomatic practices.

everything-claude-code

162.2k

compose-multiplatform-patterns

Provides patterns for shared UI in Compose Multiplatform across Android, iOS, Desktop, and Web: state management with ViewModels/StateFlow, navigation, theming, and performance.

everything-claude-code

162.2k

e2e-testing

Implements Playwright E2E testing patterns: Page Object Model, test organization, configuration, reporters, artifacts, and CI/CD integration for stable suites.

everything-claude-code

162.2k

Stats

Parent Repo Stars5

Parent Repo Forks0

Last CommitFeb 18, 2026

Actions

View Source View Plugin View on GitHub View README

Google Workspace Authentication

Authenticate the Gmail and Google Calendar MCP servers via OAuth 2.0.

Prerequisites

A Google Cloud Platform project with a Desktop-type OAuth 2.0 Client ID

Download the OAuth JSON and place it in BOTH locations:

~/.gmail-mcp/gcp-oauth.keys.json
~/.calendar-mcp/gcp-oauth.keys.json

Enable these APIs in the GCP project:

Gmail API
Google Calendar API
People API (for contact lookup)

Procedure

Verify OAuth keys exist:

ls ~/.gmail-mcp/gcp-oauth.keys.json ~/.calendar-mcp/gcp-oauth.keys.json

Create config directories if missing:

mkdir -p ~/.gmail-mcp ~/.calendar-mcp

Authenticate Gmail server (opens browser for OAuth consent):

node ${CLAUDE_PLUGIN_ROOT}/servers/gmail/index.js auth

Authenticate Calendar server:

node ${CLAUDE_PLUGIN_ROOT}/servers/calendar/index.js auth

Verify credentials were created:

ls ~/.gmail-mcp/credentials.json ~/.calendar-mcp/credentials.json

Test connectivity by running /mcp to reconnect both servers.

Report success/failure to user.

Troubleshooting

Port 3000 conflict: lsof -ti:3000 | xargs kill -9 then retry

Browser doesn't open: Copy the auth URL from terminal output manually

People API error: Ensure People API is enabled in GCP console

Token expired: Re-run this authentication flow. Tokens auto-refresh during normal use but may expire after prolonged inactivity.

Google Workspace Authentication

Authenticate the Gmail and Google Calendar MCP servers via OAuth 2.0.

Prerequisites

A Google Cloud Platform project with a Desktop-type OAuth 2.0 Client ID
Download the OAuth JSON and place it in BOTH locations:
- ~/.gmail-mcp/gcp-oauth.keys.json
- ~/.calendar-mcp/gcp-oauth.keys.json
Enable these APIs in the GCP project:
- Gmail API
- Google Calendar API
- People API (for contact lookup)

Procedure

Verify OAuth keys exist:

ls ~/.gmail-mcp/gcp-oauth.keys.json ~/.calendar-mcp/gcp-oauth.keys.json

Create config directories if missing:
```
mkdir -p ~/.gmail-mcp ~/.calendar-mcp
```
Authenticate Gmail server (opens browser for OAuth consent):
```
node ${CLAUDE_PLUGIN_ROOT}/servers/gmail/index.js auth
```

Authenticate Calendar server:

node ${CLAUDE_PLUGIN_ROOT}/servers/calendar/index.js auth

Verify credentials were created:

ls ~/.gmail-mcp/credentials.json ~/.calendar-mcp/credentials.json

Test connectivity by running /mcp to reconnect both servers.
Report success/failure to user.

Troubleshooting

Port 3000 conflict: lsof -ti:3000 | xargs kill -9 then retry
Browser doesn't open: Copy the auth URL from terminal output manually
People API error: Ensure People API is enabled in GCP console
Token expired: Re-run this authentication flow. Tokens auto-refresh during normal use but may expire after prolonged inactivity.