GCP MCP
Enables natural language querying and management of Google Cloud Platform resources including Compute Engine, Cloud Storage, Cloud Functions, Cloud Run, BigQuery, Cloud SQL, GKE clusters, Cloud Logging, and billing information across multiple GCP projects and regions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GCP MCP list all Cloud Storage buckets in my current project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GCP MCP
A Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with your Google Cloud Platform environment. This allows for natural language querying and management of your GCP resources during conversations.
Features
🔍 Query and modify GCP resources using natural language
☁️ Support for multiple GCP projects
🌐 Multi-region support
🔐 Secure credential handling (no credentials are exposed to external services)
🏃♂️ Local execution with your GCP credentials
🔄 Automatic retries for improved reliability
Related MCP server: GCP Billing and Monitoring MCP Server
Prerequisites
Node.js
Amazon Q CLI/Claude Desktop/Cursor/Windsurf
GCP credentials configured locally (application default credentials)
Installation
Clone the repository:
git clone https://github.com/RadiumGu/gcp-ops-mcp.git
cd gcp-ops-mcpInstall dependencies:
npm installBuild the project:
npm run buildConfiguration
Amazon Q CLI
Add the following configuration to your Q CLI MCP settings:
{
"mcpServers": {
"gcp-mcp": {
"command": "node",
"args": ["/path/to/gcp-ops-mcp/bin.js"],
"env": {
"NODE_PATH": "/path/to/gcp-ops-mcp/node_modules"
}
}
}
}Replace /path/to/gcp-ops-mcp with the actual path to your project directory.
Claude Desktop
Open Claude desktop app and go to Settings -> Developer -> Edit Config
Add the following entry to your
claude_desktop_config.json:
via npm:
{
"mcpServers": {
"gcp": {
"command": "sh",
"args": ["-c", "npx -y gcp-mcp"]
}
}
}If you installed from source:
{
"mcpServers": {
"gcp": {
"command": "npm",
"args": [
"--silent",
"--prefix",
"/path/to/gcp-mcp",
"start"
]
}
}
}Replace /path/to/gcp-mcp with the actual path to your project directory if using source installation.
Cursor
Open Cursor and go to Settings (⌘,)
Navigate to AI -> Model Context Protocol
Add a new MCP configuration:
{
"gcp": {
"command": "npx -y gcp-mcp"
}
}Windsurf
Open
~/.windsurf/config.json(create if it doesn't exist)Add the MCP configuration:
{
"mcpServers": {
"gcp": {
"command": "npx -y gcp-mcp"
}
}
}GCP Setup
Set up GCP credentials:
Set up application default credentials using
gcloud auth application-default login
Refresh your AI assistant (Claude Desktop/Cursor/Windsurf)
Usage
Start by selecting a project or asking questions like:
"List all GCP projects I have access to"
"Show me all Cloud SQL instances in project X"
"What's my current billing status?"
"Show me the logs from my Cloud Run services"
"List all GKE clusters in us-central1"
"Show me all Cloud Storage buckets in project X"
"What Cloud Functions are deployed in us-central1?"
"List all Cloud Run services"
"Show me BigQuery datasets and tables"
Available Tools
run-gcp-code: Execute GCP API calls using TypeScript codelist-projects: List all accessible GCP projectsselect-project: Select a GCP project for subsequent operationsget-billing-info: Get billing information for the current projectget-cost-forecast: Get cost forecast for the current projectget-billing-budget: Get billing budgets for the current projectlist-gke-clusters: List all GKE clusters in the current projectlist-sql-instances: List all Cloud SQL instances in the current projectget-logs: Get Cloud Logging entries for the current project
Example Interactions
List available projects:
List all GCP projects I have access toSelect a project:
Use project my-project-idCheck billing status:
What's my current billing status?View logs:
Show me the last 10 log entries from my projectSupported Services
Google Compute Engine
Cloud Storage
Cloud Functions
Cloud Run
BigQuery
Cloud SQL
Google Kubernetes Engine (GKE)
Cloud Logging
Cloud Billing
Resource Manager
More coming soon...
Troubleshooting
To see logs:
tail -n 50 -f ~/Library/Logs/Claude/mcp-server-gcp.logCommon issues:
Authentication errors: Ensure you've run
gcloud auth application-default loginPermission errors: Check IAM roles for your account
API errors: Verify that required APIs are enabled in your project
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT
Available Tools
9 toolsget-billing-budgetC
Get billing budgets for the current project
Inputs: projectId.
get-billing-infoC
Get billing information for the current project
Inputs: projectId.
get-cost-forecastB
Get cost forecast for the current project
Inputs: projectId, months.
get-logsB
Get Cloud Logging entries for the current project
Inputs: filter, pageSize.
list-gke-clustersB
List all GKE clusters in the current project
Inputs: location.
list-projectsA
List all GCP projects accessible with current credentials
Inputs: no named parameters.
list-sql-instancesB
List all Cloud SQL instances in the current project
Inputs: no named parameters.
run-gcp-codeD
Run GCP code
Inputs: reasoning (required), code (required), projectId, region.
select-projectB
Selects GCP project to use for subsequent interactions
Inputs: projectId (required), region.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools have distinct purposes targeting specific GCP services or functions, but 'run-gcp-code' is ambiguous and could overlap with other operations, potentially causing confusion. The other tools are clearly scoped to billing, logging, resource listing, and project selection.
The naming is mixed with inconsistent patterns: some use verb_noun (e.g., 'list-projects', 'get-logs'), others use noun_verb (e.g., 'run-gcp-code'), and hyphenation varies. While readable, it lacks a uniform convention across all tools.
With 9 tools, the count is reasonable for a GCP server, covering key areas like billing, logging, and resource management. It's slightly lean but well-scoped, avoiding bloat while providing essential functionality.
The toolset covers listing and getting operations well but has notable gaps in CRUD coverage, such as missing create, update, or delete tools for resources like GKE clusters or SQL instances. This could limit agent workflows that require full lifecycle management.
Maintenance
Related MCP Connectors
Unified API to query AWS, GCP, Azure and generate Terraform/CLI execution kits for AI agents.
The Google Compute Engine MCP server is a fully-managed Model Context Protocol server that provides tools to manage Google Compute Engine resources through AI agents. It enables capabilities including instance management (creating, starting, stopping, resetting, listing), disk management, handling instance templates and group managers, viewing machine and accelerator types, managing images, and accessing reservation and commitment information. The server operates as a zero-deployment, enterprise-grade endpoint at https://compute.googleapis.com/mcp with built-in IAM-based security.
Interact with your Google Cloud Firestore resources using natural language commands.
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with and manage Google Cloud Platform resources including Compute Engine, Cloud Run, Storage, BigQuery, and other GCP services through a standardized MCP interface.16MIT
- AlicenseCqualityDmaintenanceEnables interaction with Google Cloud services including billing cost analysis, log querying, and metrics monitoring through natural language commands. Provides comprehensive tools for managing GCP resources, analyzing costs, detecting anomalies, and retrieving operational insights.401Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables managing Google Cloud Platform infrastructure through natural language, including VM deployment, SSH key management, remote command execution, and Terraform infrastructure-as-code operations.2-
- AlicenseBqualityNot gradedmaintenanceEnables AI assistants to interact with and manage Google Cloud Platform resources including Artifact Registry, BigQuery, Cloud Build, Compute Engine, Cloud Run, Cloud Storage, and monitoring services through a standardized MCP interface.1MIT