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

@@ -15,6 +15,10 @@ Repository-wide facts for coding agents. Pattern- and agent-specific context liv
- `render_mcp_server.py`, `smoke_mcp_server.py`.
- `mcp-servers/`, `deploy/`, and `docs/`.
## MCP servers
`mcp-servers/` holds rendered servers: never edit `server.py` by hand. See `mcp-servers/README.md`. `azure-discovery`, `aws-discovery` and `gcp-discovery` take a customer credential per project; `cloud-knowledge` takes Kyndryl's, tenant-wide. They're deployed to `mcp-servers` on public Python images (not hardened; no customer data yet), are registered in the `CP1 Agentic Landing Zone` tenant (`6ae37d13999438461a529409`), aren't tested on a real cloud, and no agent declares them.
## Sources of truth
| What | Where |