GCP MCP Server
Enables querying and management of GCP resources including Artifact Registry, BigQuery, Cloud Audit Logs, Cloud Build, Compute Engine, Cloud Monitoring, Cloud Run, and Cloud Storage through a standardized interface.
Click on "Install 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 Serverlist my Cloud Storage buckets in the us-central1 region"
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.
This is not a Ready MCP Server
GCP MCP Server
A comprehensive Model Context Protocol (MCP) server implementation for Google Cloud Platform (GCP) services, enabling AI assistants to interact with and manage GCP resources through a standardized interface.
Overview
GCP MCP Server provides AI assistants with capabilities to:
Query GCP Resources: Get information about your cloud infrastructure
Manage Cloud Resources: Create, configure, and manage GCP services
Receive Assistance: Get AI-guided help with GCP configurations and best practices
The implementation follows the MCP specification to enable AI systems to interact with GCP services in a secure, controlled manner.
Supported GCP Services
This implementation includes support for the following GCP services:
Artifact Registry: Container and package management
BigQuery: Data warehousing and analytics
Cloud Audit Logs: Logging and audit trail analysis
Cloud Build: CI/CD pipeline management
Cloud Compute Engine: Virtual machine instances
Cloud Monitoring: Metrics, alerting, and dashboards
Cloud Run: Serverless container deployments
Cloud Storage: Object storage management
Architecture
The project is structured as follows:
gcp-mcp-server/
├── core/ # Core MCP server functionality auth context logging_handler security
├── prompts/ # AI assistant prompts for GCP operations
├── services/ # GCP service implementations
│ ├── README.md # Service implementation details
│ └── ... # Individual service modules
├── main.py # Main server entry point
└── ...Key components:
Service Modules: Each GCP service has its own module with resources, tools, and prompts
Client Instances: Centralized client management for authentication and resource access
Core Components: Base functionality for the MCP server implementation
Getting Started
Prerequisites
Python 3.10+
GCP project with enabled APIs for the services you want to use
Authenticated GCP credentials (Application Default Credentials recommended)
Installation
Clone the repository:
git clone https://github.com/yourusername/gcp-mcp-server.git cd gcp-mcp-serverSet up a virtual environment:
python -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activateInstall dependencies:
pip install -r requirements.txtConfigure your GCP credentials:
# Using gcloud gcloud auth application-default login # Or set GOOGLE_APPLICATION_CREDENTIALS export GOOGLE_APPLICATION_CREDENTIALS="/path/to/service-account-key.json"Set up environment variables:
cp .env.example .env # Edit .env with your configuration
Running the Server
Start the MCP server:
python main.pyFor development and testing:
# Development mode with auto-reload
python main.py --dev
# Run with specific configuration
python main.py --config config.yamlDocker Deployment
Build and run with Docker:
# Build the image
docker build -t gcp-mcp-server .
# Run the container
docker run -p 8080:8080 -v ~/.config/gcloud:/root/.config/gcloud gcp-mcp-serverConfiguration
The server can be configured through environment variables or a configuration file:
Environment Variable | Description | Default |
| Default GCP project ID | None (required) |
| Default region/zone |
|
| Server port |
|
| Logging level |
|
See .env.example for a complete list of configuration options.
Development
Adding a New GCP Service
Create a new file in the
services/directoryImplement the service following the pattern in existing services
Register the service in
main.py
See the services README for detailed implementation guidance.
Security Considerations
The server uses Application Default Credentials for authentication
Authorization is determined by the permissions of the authenticated identity
No credentials are hardcoded in the service implementations
Consider running with a service account with appropriate permissions
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
Google Cloud Platform team for their comprehensive APIs
Model Context Protocol for providing a standardized way for AI to interact with services
Using the Server
To use this server:
Place your GCP service account key file as
service-account.jsonin the same directoryInstall the MCP package:
pip install "mcp[cli]"Install the required GCP package:
pip install google-cloud-runRun:
mcp dev gcp_cloudrun_server.py
Or install it in Claude Desktop:
mcp install gcp_cloudrun_server.py --name "GCP Cloud Run Manager"MCP Server Configuration
The following configuration can be added to your configuration file for GCP Cloud Tools:
"mcpServers": {
"GCP Cloud Tools": {
"command": "uv",
"args": [
"run",
"--with",
"google-cloud-artifact-registry>=1.10.0",
"--with",
"google-cloud-bigquery>=3.27.0",
"--with",
"google-cloud-build>=3.0.0",
"--with",
"google-cloud-compute>=1.0.0",
"--with",
"google-cloud-logging>=3.5.0",
"--with",
"google-cloud-monitoring>=2.0.0",
"--with",
"google-cloud-run>=0.9.0",
"--with",
"google-cloud-storage>=2.10.0",
"--with",
"mcp[cli]",
"--with",
"python-dotenv>=1.0.0",
"mcp",
"run",
"C:\\Users\\enes_\\Desktop\\mcp-repo-final\\gcp-mcp\\src\\gcp-mcp-server\\main.py"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "C:/Users/enes_/Desktop/mcp-repo-final/gcp-mcp/service-account.json",
"GCP_PROJECT_ID": "gcp-mcp-cloud-project",
"GCP_LOCATION": "us-east1"
}
}
}Configuration Details
This configuration sets up an MCP server for Google Cloud Platform tools with the following:
Command: Uses
uvpackage manager to run the serverDependencies: Includes various Google Cloud libraries (Artifact Registry, BigQuery, Cloud Build, etc.)
Environment Variables:
GOOGLE_APPLICATION_CREDENTIALS: Path to your GCP service account credentialsGCP_PROJECT_ID: Your Google Cloud project IDGCP_LOCATION: GCP region (us-east1)
Usage
Add this configuration to your MCP configuration file to enable GCP Cloud Tools functionality.
Available Tools
1 tooltest_gcp_authC
Test GCP authentication
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action ('test') without disclosing behavioral traits like what gets tested (e.g., credentials, permissions), the output format, error conditions, or side effects. This is inadequate for a tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient phrase with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and a simple purpose, the description is incomplete. It doesn't explain what 'test' means in practice, what results to expect, or any prerequisites, leaving significant gaps for an AI agent to understand the tool's behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, earning a baseline score of 4 for not introducing confusion or redundancy.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Test GCP authentication' states a clear action (test) and target (GCP authentication), but it's vague about what 'test' entails—does it validate credentials, check permissions, or verify connectivity? With no siblings, differentiation isn't needed, but the purpose could be more specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool—for example, after configuration changes, before other operations, or for troubleshooting. With no sibling tools, alternatives aren't relevant, but the description lacks any context for its application.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'test_gcp_auth' has a clearly distinct and singular purpose.
The naming follows a consistent snake_case pattern with a verb_noun structure ('test_gcp_auth'). With only one tool, consistency is inherently perfect as there are no other tools to compare against.
A single tool is too few for a server named 'GCP MCP Server', which implies broader Google Cloud Platform functionality. This minimal toolset severely limits the server's utility and scope, making it feel incomplete and underpowered for its apparent domain.
The tool surface is severely incomplete for a GCP server. It only provides authentication testing, with no tools for core GCP operations like managing compute instances, storage, databases, or other cloud services, leaving significant gaps that will cause agent failures.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
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.
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
The BigQuery remote MCP server is a fully managed service that uses the Model Context Protocol to connect AI applications and LLMs to BigQuery data sources. It provides secure, standardized tools for AI agents to list datasets and tables, retrieve schemas, generate and execute SQL queries through natural language, and analyze data—enabling direct access to enterprise analytics data without requiring manual SQL coding.
Connect MCP clients to 2,000+ AI models without managing provider API keys.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MCP-Mirror/enesbol_gcp-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server