Skip to main content
Glama

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.

Related MCP server: gcloud MCP Cloud Run

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

  1. Clone the repository:

    git clone https://github.com/yourusername/gcp-mcp-server.git
    cd gcp-mcp-server
  2. Set up a virtual environment:

    python -m venv venv
    source venv/bin/activate  # On Windows: venv\Scripts\activate
  3. Install dependencies:

    pip install -r requirements.txt
  4. Configure 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"
  5. Set up environment variables:

    cp .env.example .env
    # Edit .env with your configuration

Running the Server

Start the MCP server:

python main.py

For development and testing:

# Development mode with auto-reload
python main.py --dev

# Run with specific configuration
python main.py --config config.yaml

Docker 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-server

Configuration

The server can be configured through environment variables or a configuration file:

Environment Variable

Description

Default

GCP_PROJECT_ID

Default GCP project ID

None (required)

GCP_DEFAULT_LOCATION

Default region/zone

us-central1

MCP_SERVER_PORT

Server port

8080

LOG_LEVEL

Logging level

INFO

See .env.example for a complete list of configuration options.

Development

Adding a New GCP Service

  1. Create a new file in the services/ directory

  2. Implement the service following the pattern in existing services

  3. 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.

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add some amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. 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:

  1. Place your GCP service account key file as service-account.json in the same directory

  2. Install the MCP package: pip install "mcp[cli]"

  3. Install the required GCP package: pip install google-cloud-run

  4. Run: 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 uv package manager to run the server

  • Dependencies: Includes various Google Cloud libraries (Artifact Registry, BigQuery, Cloud Build, etc.)

  • Environment Variables:

    • GOOGLE_APPLICATION_CREDENTIALS: Path to your GCP service account credentials

    • GCP_PROJECT_ID: Your Google Cloud project ID

    • GCP_LOCATION: GCP region (us-east1)

Usage

Add this configuration to your MCP configuration file to enable GCP Cloud Tools functionality.

Available Tools

1 tool
test_gcp_authC

Test GCP authentication

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions 'test' but doesn't disclose behavioral traits like what gets tested (e.g., credentials, permissions), whether it's safe/destructive, or what output to expect. This leaves significant gaps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('Test GCP authentication') with no wasted words, making it front-loaded and easy to parse. It efficiently conveys the core purpose in minimal text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple auth test) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'test' entails, what success/failure looks like, or any behavioral context, leaving the agent with insufficient information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info, but that's acceptable here, meeting the baseline for zero-param tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Test GCP authentication' states a clear purpose (testing authentication) but lacks specificity about what resource or system is being tested. It doesn't distinguish from siblings (though none exist), making it somewhat vague but functional.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool, such as during setup, troubleshooting, or validation scenarios. With no siblings, differentiation isn't needed, but general usage context is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'test_gcp_auth' has a clear and distinct purpose that cannot be mistaken for any other tool in this set.

Naming Consistency5/5

The naming pattern is perfectly consistent as there is only one tool. It follows a verb_noun structure ('test_gcp_auth'), and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.

Tool Count2/5

The tool count of 1 is too few for a server named 'GCP MCP Server', which suggests a broad scope covering Google Cloud Platform services. A single authentication test tool is insufficient for meaningful interaction with GCP resources, making this a significant mismatch in scope.

Completeness1/5

The tool surface is severely incomplete for a GCP server. It only provides an authentication test, lacking any operations for core GCP services like compute, storage, databases, or management. This leaves major gaps that will prevent agents from performing useful tasks in the domain.

Maintenance

ActivityInactive
ResponsivenessSyncing

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.

  • Connect MCP clients to 2,000+ AI models without managing provider API keys.

  • 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.

Related MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    Enables AI assistants to interact with Google Cloud Platform resources through natural language queries. Supports querying and managing GCP services like Compute Engine, Cloud Storage, BigQuery, and more across multiple projects and regions.
    9
    9,698
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Google Cloud Platform services through gcloud CLI commands via a Cloud Run deployed MCP server. Supports executing gcloud commands and managing GCP resources through natural language.
    MIT
  • A
    license
    B
    quality
    Not graded
    maintenance
    Enables 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.
    1

Latest Blog Posts

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/enesbol/gcp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server