google-cloud-platform-mcp.yml

Endpoint

Hosted endpoint · transport

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

Tool quality observed · not scored

Heaviest: run_gcloud_command 1850, run_bq_command 1697

From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.

Tools

• run_gcloud_command — Executes a single gcloud CLI command within the user's Google Cloud project. **CRITICAL SAFETY WARNING (POTENTIALLY DESTRUCTIVE)**: This tool can create, update, or delete Google Cloud resources (e.g., gcloud compute instances delete). It is NOT restricted to read-only commands. Use extreme caution. **FORBIDDEN COMMANDS**: An agent MUST NOT execute the following gcloud commands (including their alpha/beta variants): `app deploy`, `app instances ssh`, `auth`, `billing`, `components`, `config`, `docker`, `feedback`, `info`, `init`, `meta`, `survey`. **STRICT EXECUTION RULES**: 1. You MUST provide the 'project' parameter (i.e. project="projects/PROJECT_ID") when using this tool (it is used for Cloud CLI Execution API enablement check, billing, quota, etc.). This is NOT the same as the --project flag in gcloud commands used to specify the project gcloud operates on. 2. Flag Formatting: You MUST always use an '=' sign to separate flag keys from their values for all long options. Correct: `--zone=us-central1-a` or `--project=my-project`. Incorrect: `--zone us-central1-a` or `--project my-project`. 3. Billing Project: You cannot assume any pre-configured project or billing settings in the execution environment. For non-project scoped commands (e.g., folder or organization level) or specific scenarios like Cloud Storage Requester Pays, you MUST pass the `--billing-project=PROJECT` flag. For project-scoped commands, you MAY additionally specify `--billing-project=PROJECT` to override the quota project, which will take effect for Google Cloud APIs that do not support resource-project-override. 4. Project Scope: You SHOULD ALWAYS pass the `--project=PROJECT_ID` flag for project-scoped commands. Do not use it for organization or folder-level commands. If you do not provide a `--project flag` for a project-scoped command, the resource project will default to the project set in the `--billing-project` flag. 5. If specifying `--billing-project` flag in the gcloud command, ensure that the value is a project ID or a project number. The value MUST NOT be a special value (ie LEGACY, CURRENT_PROJECT, CURRENT_PROJECT_WITH_FALLBACK). 6. At least one of `--project` or `--billing-project` MUST be specified in the command string. 7. Asynchronous Operations: For long-running synchronous operations (e.g., creating a VM or a database), you SHOULD ALWAYS pass the `--async` flag to prevent agent timeouts. 8. Log Rate Limiting: When using `gcloud logging read`, you MUST ALWAYS include a `--limit` flag (e.g., `--limit=100`) to prevent credential and connection timeouts. 9. Self-Correction: If a command returns an error, analyze stdout and stderr, correct the syntax or flags, and retry in the next iteration. Be aware that stderr is not strictly used for errors and a command may succeed even when stderr has content. 10. input_files: (Optional) A list of files to be created in the environment before running the command. Each file must have a 'path' (relative to the current directory) and 'contents'. The 'contents' must be plain text representing the file's content. This is useful for commands that read from files (e.g. `gcloud builds submit --config=cloudbuild.yaml --async --project=PROJECT_ID`). Example gcloud commands/patterns: 1. Read Compute Engine instance logs with severity>=ERROR: `gcloud logging read "severity>=ERROR AND resource.type='gce_instance'" --limit=10 --order=DESC --project=PROJECT_ID` - Note the use of quotes for the filter expression. 2. List all PSC endpoints: `gcloud compute forwarding-rules list --project=PROJECT_ID` 3. Describe a PSC endpoint: `gcloud compute forwarding-rules describe FORWARDING_RULE_NAME --region=REGION --project=PROJECT_ID` - Note the use of '=' for the --region flag. 4. List all clusters: `gcloud container clusters list --project=PROJECT_ID` 5. Describe a cluster: `gcloud container clusters describe CLUSTER_NAME --region=REGION --project=PROJECT_ID` 6. List compute instances: `gcloud compute instances list --project=PROJECT_ID` 7. Get IAM policy for a project: `gcloud projects get-iam-policy PROJECT_ID --project=PROJECT_ID` Response strings are formatted for terminal output by default (stdout or stderr). Use --format flag to change the format.
• run_bq_command — Runs a single [BigQuery CLI (bq) command](https://docs.cloud.google.com/bigquery/docs/reference/bq-cli-reference). This tool allows you to run any bq command in the user's project, including commands that create, update, or delete Google Cloud resources (i.e., mutations). **CRITICAL SAFETY WARNING (POTENTIALLY DESTRUCTIVE)**: This tool can create, update, or delete BigQuery resources (e.g., `bq rm`, `bq cancel`, `bq query`). It is NOT restricted to read-only commands. Use extreme caution. **FORBIDDEN COMMANDS**: An agent MUST NOT execute the following bq commands: `bq init`, `bq pyshell`, `bq shell`. **STRICT EXECUTION RULES**: 1. At least one of `--project_id` or `--quota_project_id` MUST be specified in the command string. 2. Project ID vs Quota Project: The --project_id flag specifies the resource project the command operates on (mirrors gcloud's --project flag). The --quota_project_id flag specifies the project charged for billing/quota of the downstream BigQuery API call (mirrors gcloud's `--billing-project` flag). If `--project_id` is specified in the command, it will be used as the billing/quota project. If `--project_id` is not specified OR `--quota_project_id` is additionally specified, the billing/quota project will be the project set in the `--quota_project_id` flag. 3. Flag Formatting: You MUST always use an '=' sign to separate flag keys from their values for all long options. Correct: `'--project_id=my-project'` or `'--location=us'`. Incorrect: `'--project_id my-project'` or `'--location us'`. Do not use spaces between flags and their values. 4. No Configuration Defaults: The bq command is executed in a stateless manner; it does not load local configuration files like .bigqueryrc. Therefore, for all regional operations (e.g., creating a dataset or querying a regional dataset), you MUST explicitly specify the `--location` flag (e.g., `--location=us` or `--location=EU`). 5. Asynchronous Operations: Some commands initiate synchronous long-running operations (e.g., running query jobs). You SHOULD ALWAYS pass the `--nosync` flag for these commands to prevent agent timeouts. 6. Command Restrictions: You MUST NOT use the following bq commands: `bq init`, `bq pyshell`, `bq shell`. Command piping or chaining is NOT supported. 7. Self-Correction: If a command returns an error, analyze stdout and stderr, correct the syntax or flags, and retry in the next iteration. Be aware that stderr is not strictly used for errors and a command may succeed even when stderr has content. Examples of mutating bq commands include: `bq mk`, `bq rm`, `bq update`, `bq insert`, `bq query` (without `--dry_run`), etc. Usage: `RunBq(command="bq query --project_id=PROJECT_ID 'SELECT 1'", project="projects/PROJECT_ID", input_files=[{"path": "PATH", "contents": "CONTENTS"}])` You MUST provide the full bq command as a single string in the 'command' parameter. You MUST provide the 'project' parameter (format: projects/PROJECT_ID) as the API execution project for billing, API enablement, and quota consumption checks. Example bq commands/patterns: 1. Run a query: `bq query --use_legacy_sql=false --project_id=PROJECT_ID 'SELECT * FROM `project.dataset.table` LIMIT 10'` 2. Create a dataset: `bq mk --dataset --location=us --project_id=PROJECT_ID myDataset` 3. Create a table: `bq mk --table --project_id=PROJECT_ID myDataset.myTable name:string,value:integer` 4. Remove a dataset: `bq rm -f --dataset --project_id=PROJECT_ID myDataset` 5. Remove a table: `bq rm -f -t --project_id=PROJECT_ID myDataset.myTable` 6. Update table description: `bq update --description="New description" --project_id=PROJECT_ID myDataset.myTable` 7. List datasets in a project: `bq ls --datasets=true --project_id=PROJECT_ID`

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

curl "https://apis.io/api/v1/mcp/google-cloud-platform-mcp-yml"

curl "https://apis.io/api/v1/mcp?limit=25"