Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/jpantsjoha/googlecloud-plugin/mcp-serversnpx skills add jpantsjoha/googlecloud-plugin --skill mcp-serversgit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00088 | $0.01446 |
| Opus 5 | $0.00044 | $0.00723 |
| Sonnet 5 | $0.00018 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
mcp-servers scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Servers — Google Cloud
Configure and maintain Model Context Protocol (MCP) servers for Google Cloud. All auth flows through ADC or explicit SA key path — no credential values stored anywhere.
Auth Architecture
All GCP MCP servers authenticate via Application Default Credentials (ADC):
# Authenticate locally (developer machine)
gcloud auth application-default login
# Authenticate for a service account (CI/CD or production agent)
gcloud auth activate-service-account --key-file=/path/to/sa-key.json
gcloud auth application-default login [email protected]
What the plugin ships vs what you opt into
The portable mcp.json (Agent Plugins 1.0.0) declares one server — gcloud
— because that is the only one that starts with no user-supplied configuration:
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
"mcpServers": {
"gcloud": { "type": "stdio", "command": "npx", "args": ["-y", "@google-cloud/gcloud-mcp"] }
}
}
Two consequences worth knowing:
- No
envblock. Agent Plugins expands only${PLUGIN_ROOT}and${PLUGIN_DATA}. A${GCP_PROJECT_ID}placeholder would be passed through literally and mis-set your project. Export it in your own shell instead — the client passes the ambient environment through:export CLOUDSDK_CORE_PROJECT=your-project-id gcloud auth application-default login - The capability table below lists logical GCP capabilities, not entries in
mcp.json. Most are reachable through thegcloudserver; anything needing its own config file is an opt-in you add to your client's own MCP settings.
Google-Managed MCP Servers (v0.1)
| Server | Capability | Required Role |
|---|---|---|
google-cloud-run |
Deploy/manage Cloud Run services | roles/run.admin |
google-bigquery |
Query/manage BigQuery datasets | roles/bigquery.user |
google-gke |
GKE cluster management | roles/container.developer |
google-storage |
Cloud Storage bucket ops | roles/storage.objectAdmin |
google-vertex-ai |
Vertex AI model/endpoint management | roles/aiplatform.user |
google-iam |
IAM policy management | roles/iam.securityAdmin |
google-logging |
Cloud Logging query/ingest | roles/logging.viewer |
google-monitoring |
Metrics, alerting | roles/monitoring.viewer |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 124 lines · 88 tokens per session scan A 4bf8c82c5140
mcp-servers is a skill published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 88 tokens to every session and 1,446 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…
serving-llms-vllm
Use when deploying production LLM APIs, optimizing inference latency/throughput, or serving models with limited GPU memory. Supports OpenAI-compatible endpoints, quantization (GPTQ/AWQ/FP8), and tensor parallelism.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".