gcp-mcp-server
Model Context Protocol server for Google Cloud Platform, enabling interaction with Resource Manager, Compute Engine, Cloud Storage, BigQuery, Pub/Sub, and Cloud Logging via natural language.
README
gcp-mcp-server
Model Context Protocol server for Google Cloud Platform. Built on the MCP
Python SDK (mcp>=1.27) using FastMCP, with tools that touch Resource
Manager, Compute Engine, Cloud Storage, BigQuery, Pub/Sub, and Cloud Logging.
Features
- Application Default Credentials (ADC) or explicit service-account JSON auth
- Lazy-constructed Google Cloud SDK clients bound to resolved credentials
- Blocking SDK calls executed in worker threads via
anyio.to_thread.run_sync - Typed tools covering the most common GCP day-to-day operations
- Unit tests that mock the SDK clients end-to-end (no real API calls)
Install
git clone https://github.com/asklokesh/gcp-mcp-server.git
cd gcp-mcp-server
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
Requires Python 3.10 or newer.
Authentication
The server resolves credentials in the following order:
- If
GCP_CREDENTIALS_PATHpoints to a service-account JSON file, that file is used. - Otherwise, Application Default Credentials (ADC) are loaded via
google.auth.default().
For ADC, the simplest path is:
gcloud auth application-default login
Or point GOOGLE_APPLICATION_CREDENTIALS at a service-account JSON file.
Environment variables
All settings are optional and use the GCP_ prefix:
| Variable | Description | Default |
|---|---|---|
GCP_DEFAULT_PROJECT_ID |
Project id used when a tool doesn't receive one | unset |
GCP_CREDENTIALS_PATH |
Path to a service-account JSON file | unset (ADC) |
GCP_TIMEOUT |
Default per-request timeout in seconds | 60 |
Claude Desktop configuration
Add an entry like this to your Claude Desktop mcpServers config:
{
"mcpServers": {
"gcp": {
"command": "gcp-mcp",
"env": {
"GCP_DEFAULT_PROJECT_ID": "my-gcp-project",
"GCP_CREDENTIALS_PATH": "/absolute/path/to/service-account.json"
}
}
}
}
If you prefer ADC, omit GCP_CREDENTIALS_PATH and ensure
gcloud auth application-default login was run as the same user that
launches Claude Desktop.
Tools
Resource Manager / IAM
list_projects()- list visible GCP projectsget_project(project_id)- fetch project metadatalist_service_accounts(project_id)- list IAM service accounts via the IAM REST API
Compute Engine
list_instances(project_id?, zone?)- zonal or aggregated instance listget_instance(project_id, zone, name)- single instance detailsstart_instance(project_id, zone, name)- start a VMstop_instance(project_id, zone, name)- stop a VM
Cloud Storage
list_buckets(project_id?)- list buckets in a projectlist_objects(bucket, prefix?, max_results=100)- list blobsget_object_metadata(bucket, name)- fetch blob metadata
BigQuery
list_datasets(project_id?)- list datasetslist_tables(project_id, dataset)- list tablesquery_bigquery(project_id, sql, dry_run=False)- run a query; dry-run returns schema and estimated bytes
Pub/Sub
list_topics(project_id?)- list topicslist_subscriptions(project_id?)- list subscriptionspublish_message(project_id, topic, data, attributes?)- publish a message.datais UTF-8; prefix withbase64:for binary payloads.
Cloud Logging
read_logs(project_id, filter, max_entries=50)- advanced log filter, e.g.resource.type="gce_instance"
Required IAM roles
The caller's principal needs appropriate roles per surface. Minimal recommended roles:
| Surface | Role(s) |
|---|---|
| Resource Manager | roles/resourcemanager.projectViewer, roles/browser |
| IAM | roles/iam.serviceAccountViewer |
| Compute | roles/compute.viewer, roles/compute.instanceAdmin.v1 (for start/stop) |
| Cloud Storage | roles/storage.objectViewer, roles/storage.bucketViewer |
| BigQuery | roles/bigquery.dataViewer, roles/bigquery.jobUser |
| Pub/Sub | roles/pubsub.viewer, roles/pubsub.publisher |
| Cloud Logging | roles/logging.viewer (or roles/logging.privateLogViewer) |
Grant only what the caller actually needs.
Development
Run the test suite:
source .venv/bin/activate
pytest -x --tb=short
Lint:
ruff check src/ tests/
Tests mock each Google Cloud client with unittest.mock, so no real
GCP APIs are called.
Project layout
src/gcp_mcp/
__init__.py # main entry point
auth.py # ADC / service-account credential resolution
clients.py # lazy SDK client construction
config.py # pydantic-settings config (GCP_ env prefix)
exceptions.py # GCPError, AuthenticationError, APIError, NotFoundError
server.py # FastMCP server + @mcp.tool() definitions
tests/ # unit tests with mocked SDK clients
pyproject.toml
requirements.txt
License
MIT.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.