Add hyperscaler discovery MCP servers and Well-Architected guidance
Some checks failed
check agents / check (push) Failing after 12s

azure-discovery, aws-discovery and gcp-discovery collect read-only metadata
on servers, workloads, Kubernetes clusters, networks, data stores, policies
and provider recommendations. Credentials arrive per call from the vault.
Replies are paged, scrubbed of secrets and anonymised, and throttled calls
back off. cloud-knowledge searches each provider's Well-Architected guidance
from fixed lists only, so no customer detail can leave the platform.

Adds shared skills, the render and test tooling, a public Python Dockerfile
until the hardened base image is reachable, the customer access guide, the
implementation plan and the Vault Service platform issue.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-30 20:11:57 +00:00
parent 416c66ced4
commit c14a94f33b
91 changed files with 13296 additions and 1 deletions

View File

@@ -0,0 +1,62 @@
# ============================================
# Google Cloud Discovery - Environment Variables
# ============================================
# Generated by Agent Builder Platform
#
# SETUP INSTRUCTIONS:
# 1. Copy this file to .env: cp .env.example .env
# 2. Generate a secure API key: openssl rand -hex 32
# 3. Update MCP_REGISTRATION_API_KEY with the generated key
# 4. Build the image from the Dockerfile and run it where the MCP Gateway
# can reach it (see README.md)
#
# MCP GATEWAY INTEGRATION:
# When registering with the MCP Gateway, use the URL the Gateway reaches this
# server at; for a container on the Gateway's network, its container name:
# http://google-cloud-discovery:8113
# ============================================
# Server Identity
MCP_SERVER_NAME=Google Cloud Discovery
MCP_SERVER_ID=gcp-discovery
MCP_SERVER_VERSION=0.1.1
# Server Configuration
MCP_SERVER_PORT=8113
# Logging: level (DEBUG, INFO, WARNING, ERROR) and format
# (json = one object per line, for log stores; console = for reading by eye)
LOG_LEVEL=INFO
LOG_FORMAT=json
# ============================================
# AUTHENTICATION (REQUIRED for production!)
# ============================================
# This key authenticates MCP Gateway requests to this server.
# The Gateway stores this key and includes it in all tool/call requests.
#
# Generate a secure key:
# openssl rand -hex 32
#
# IMPORTANT: Keep this key secret! It's stored in:
# - This .env file (gitignored)
# - MCP Gateway database (encrypted)
MCP_REGISTRATION_API_KEY=<generate one: openssl rand -hex 32>
# Set to "false" ONLY for local development/testing
# WARNING: Disabling auth in production is a security risk!
REQUIRE_AUTH=true
# ============================================
# CREDENTIALS FOR THE UPSTREAM (sent with each request, not set here)
# ============================================
# The MCP Gateway sends the tenant's credential with each call, from the Vault Service.
# true: a call without one is refused. Set to false only for local runs, where the
# server may use its own environment.
REQUIRE_VAULT_CONNECTION=true
# ============================================
# Add your own settings below
# ============================================
# Credentials for the upstream are not set here: the gateway sends them with each request.
# EXAMPLE_SETTING=value