Files
cp1-agents/mcp-servers
Jonathan Boniface c14a94f33b
Some checks failed
check agents / check (push) Failing after 12s
Add hyperscaler discovery MCP servers and Well-Architected guidance
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>
2026-10-30 20:11:57 +00:00
..

MCP servers

Server Port What it does Credential
azure-discovery 8111 Read-only discovery of an Azure estate The customer's, per project
aws-discovery 8112 Read-only discovery of an AWS estate The customer's, per project
gcp-discovery 8113 Read-only discovery of a Google Cloud estate The customer's, per project
cloud-knowledge 8114 Well-Architected guidance from each hyperscaler Kyndryl's, tenant-wide
alz-discovery-sample 8110 The Meridian sample estate, for evals None

Customers grant access as described in docs/customer-cloud-access.md.

Working on a server

A server's folder is rendered: don't edit server.py by hand. The sources are:

Path What it holds
<server>.server.yaml The definition: tools, connection fields, added packages
_common/tool_support.py Redaction, anonymisation, paging and evidence, inlined into every server
_common/<provider>_support.py Each provider's code
_common/test_contract.py The rules every server must pass
<server>/tests/test_*.py That server's own tests

After changing a source, render and test:

python3 scripts/render_mcp_server.py mcp-servers/<server>.server.yaml --out mcp-servers/<server> \
  --platform ~/platform-engineering/kyndryl-agent-builder/modernization-platform
python3 scripts/test_mcp_servers.py <server>

Rules

  • Store a discovery server's connection per project, never tenant-wide. The gateway uses a tenant-wide credential for every project without its own, so one customer's access would serve another's engagement.
  • Store cloud-knowledge's connection tenant-wide. It holds only Kyndryl's access.
  • Read-only. Don't add a tool that creates, changes or deletes anything.
  • Every reply goes through _scrub, which removes secrets and anonymises people.
  • Knowledge queries come only from the fixed lists in _common/knowledge_support.py. Never add a free-text field.