GCP MCP

Created By
eniayomia year ago
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.
Overview

what is GCP MCP?

GCP MCP is a Model Context Protocol server that allows AI assistants like Claude to interact with Google Cloud Platform (GCP) environments, enabling natural language querying and management of GCP resources during conversations.

how to use GCP MCP?

To use GCP MCP, clone the repository, install dependencies, configure your AI assistant, and start querying your GCP resources using natural language commands.

key features of GCP MCP?

  • 🔍 Query and modify GCP resources using natural language
  • ☁️ Support for multiple GCP projects
  • 🌐 Multi-region support
  • 🔐 Secure credential handling
  • 🏃‍♂️ Local execution with GCP credentials
  • 🔄 Automatic retries for improved reliability

use cases of GCP MCP?

  1. Managing GCP resources through conversational queries.
  2. Checking billing status and forecasts for GCP projects.
  3. Listing and managing Cloud SQL instances and GKE clusters.

FAQ from GCP MCP?

  • Can GCP MCP manage all GCP services?

Yes! GCP MCP supports various services including Compute Engine, Cloud Storage, Cloud Functions, and more.

  • Is GCP MCP free to use?

Yes! GCP MCP is free to use, but you will need a GCP account to access your resources.

  • How do I troubleshoot issues with GCP MCP?

Check the logs for errors and ensure your GCP credentials are correctly configured.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
eniayomi
Star
61
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago