Evan
c25a321e88
* fix: pin npm package versions in MCP integration templates Prevent supply chain attacks by pinning exact versions instead of using unpinned `npx -y @package` which pulls latest on every run. 23 of 25 integrations pinned. sqlite-mcp and aws skipped (packages not found on npm registry). * fix: use stable azure/mcp version instead of beta
29 lines
1.1 KiB
TOML
29 lines
1.1 KiB
TOML
id = "gcp-mcp"
|
|
name = "Google Cloud Platform"
|
|
description = "Manage GCP resources including Compute Engine, Cloud Storage, and BigQuery through the MCP server"
|
|
category = "cloud"
|
|
icon = "🌐"
|
|
tags = ["cloud", "google", "infrastructure", "gce", "gcs", "bigquery", "devops"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "@google-cloud/gcloud-mcp@0.5.3"]
|
|
|
|
[[required_env]]
|
|
name = "GOOGLE_APPLICATION_CREDENTIALS"
|
|
label = "Service Account Key Path"
|
|
help = "Absolute path to a GCP service account JSON key file"
|
|
is_secret = false
|
|
get_url = "https://console.cloud.google.com/iam-admin/serviceaccounts"
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Go to the GCP Console > IAM & Admin > Service Accounts (https://console.cloud.google.com/iam-admin/serviceaccounts) and create a new service account with the necessary roles.
|
|
2. Generate a JSON key file for the service account and save it to a secure location on your filesystem.
|
|
3. Enter the absolute path to the JSON key file in the GOOGLE_APPLICATION_CREDENTIALS field above.
|
|
"""
|