Help us improve
Share bugs, ideas, or general feedback.
From gcloud-tools
Configures GCloud CLI authentication: checks installation, installs if needed via brew/curl/download, authenticates user and ADC, sets default project, verifies setup for MCP.
npx claudepluginhub ruslands/plugins --plugin gcloud-toolsHow this command is triggered — by the user, by Claude, or both
Slash command
/gcloud-tools:setupThe summary Claude sees in its command listing — used to decide when to auto-load this command
# GCloud Tools Setup **Source:** [googleapis/gcloud-mcp](https://github.com/googleapis/gcloud-mcp) Check GCloud MCP status and configure CLI authentication if needed. ## Step 1: Check gcloud CLI Run: `gcloud --version` If not installed: Continue to Step 2. If installed: Skip to Step 3. ## Step 2: Install gcloud CLI Tell the user: ## Step 3: Authenticate Run these commands: Both commands will open a browser for authentication. ## Step 4: Set Default Project ## Step 5: Verify Setup Run: `gcloud auth list` Should show your authenticated account with asterisk (\*). ## Step ...
/setupConfigures GCloud CLI authentication: checks installation, installs if needed via brew/curl/download, authenticates user and ADC, sets default project, verifies setup for MCP.
/gws-installInstalls Google Workspace CLI (gws) on the current machine using existing OAuth credentials from a previous setup.
/setupConfigures Azure MCP server with Azure CLI authentication. Checks prerequisites (Azure CLI, Node.js), provides install guides if missing, verifies login, and confirms .mcp.json config.
/setupVerifies gcloud CLI installation and GCP credentials, writes gcp-inspector connector config to ~/.config/claude-grc/connectors/gcp-inspector.yaml, and runs read-only health check. Idempotent; supports --project and --region flags.
/gcp-researchResearches Google Cloud services, architecture patterns, security, compliance, and costs for a topic or use case via MCP tools. Launches agent to produce summary report.
/setup-mcpGuides interactive MCP server setup wizard: checks prerequisites like uvx, backs up configs, verifies plugin installation, configures optional API keys.
Share bugs, ideas, or general feedback.
Source: googleapis/gcloud-mcp
Check GCloud MCP status and configure CLI authentication if needed.
Run: gcloud --version
If not installed: Continue to Step 2. If installed: Skip to Step 3.
Tell the user:
Install Google Cloud SDK:
macOS (Homebrew):
brew install google-cloud-sdk
macOS/Linux (Manual):
curl https://sdk.cloud.google.com | bash
exec -l $SHELL
Windows:
Download from: https://cloud.google.com/sdk/docs/install
After install, restart your terminal.
Run these commands:
# Login with your Google account
gcloud auth login
# Set up Application Default Credentials (required for MCP)
gcloud auth application-default login
Both commands will open a browser for authentication.
# List available projects
gcloud projects list
# Set default project
gcloud config set project YOUR_PROJECT_ID
Run: gcloud auth list
Should show your authenticated account with asterisk (*).
Tell the user:
After authentication:
1. Exit Claude Code
2. Run `claude` again
The MCP will use your gcloud credentials.
If GCloud MCP fails:
Common fixes:
1. ADC not found - Run gcloud auth application-default login
2. Project not set - Run gcloud config set project PROJECT_ID
3. Permission denied - Check IAM roles in Cloud Console
4. Quota exceeded - Check quotas in Cloud Console
5. Token expired - Run gcloud auth application-default login again
If user doesn't need GCloud integration:
To disable this plugin:
1. Run /mcp command
2. Find the gcloud-observability server
3. Disable it
This prevents errors from missing authentication.