integration-gcp

Connect Google Cloud MCP servers to a self-hosted Hermes agent over SSH.

13|1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/paarths-collab/hstack --skill integration-gcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-gcp
Source: https://github.com/paarths-collab/hstack/tree/main/skills/integration-gcp
Command: npx skills add https://github.com/paarths-collab/hstack --skill integration-gcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of wiring Google Cloud services into a self-hosted Hermes agent, especially when the connection depends on SSH access, service accounts, OAuth login, and hourly token renewal.

Core Features & Use Cases

  • Managed Remote MCP Setup: Connects Google Cloud products such as BigQuery, Cloud SQL, Cloud Storage, Cloud Run, Logging, Compute, and GKE through Google’s first-party MCP endpoints.
  • Secure Authentication Handling: Uses short-lived OAuth2 bearer tokens, service-account impersonation, and a refresh cron so access does not expire after the first hour.
  • Operational Safety: Includes idempotency checks, dry-run preview, gateway reload steps, smoke tests, and rollback logic to reduce deployment mistakes.
  • Use Case: A developer wants Hermes on a VPS to query BigQuery and manage Cloud Run resources from Claude Code or Cursor without manually maintaining brittle API credentials.

Quick Start

Ask the agent to connect your chosen Google Cloud product to the self-hosted Hermes instance over SSH, grant the requested IAM role, and complete the one-time gcloud login when prompted.

Frequently Asked Questions about integration-gcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Google Cloud services to a self-hosted Hermes agent over SSH?

Connecting Google Cloud services to a self-hosted Hermes agent over SSH involves using short-lived OAuth2 bearer tokens, service-account impersonation, and a refresh cron to maintain access to managed remote MCP servers for products like BigQuery and Cloud Run.

Can I use OAuth2 service account impersonation to manage BigQuery through a remote MCP server?

Yes, OAuth2 service-account impersonation enables a Hermes agent to query BigQuery and manage Cloud Run resources via Google Cloud managed remote MCP servers, using a refresh cron to renew short-lived bearer tokens hourly.

What's the best way to prevent Google Cloud MCP token expiration in a self-hosted agent?

Preventing Google Cloud MCP token expiration requires configuring an automated refresh cron to continuously renew short-lived OAuth2 bearer tokens, ensuring persistent access to managed remote MCP servers without manual intervention.

Do I need to manually configure IAM role bindings and gateway reloads for Google Cloud MCP integrations?

No, configuring IAM role bindings, gateway reloads, and smoke tests are handled through operational safety features, including dry-run previews and rollback logic to reduce deployment mistakes when connecting remote MCP servers.

Does this Google Cloud MCP connection approach support Cloud SQL, GKE, and Pub/Sub integrations?

Yes, this Google Cloud MCP connection approach supports Cloud SQL, GKE, Pub/Sub, Spanner, AlloyDB, Firestore, Logging, Cloud Storage, and Compute Engine integrations through Google's first-party managed remote MCP endpoints over SSH.

Why do my Google Cloud MCP integrations fail after the first hour of deployment?

Google Cloud MCP integrations fail after the first hour because initial OAuth2 bearer tokens expire; setting up an automated refresh cron for short-lived tokens resolves this authentication timeout.