- Scripts to run workflows from a YAML context or run inputs (kab_run_workflow.py, with --input name=@file), store per-project discovery connections, bootstrap agent MCP keys, refresh the KAB token, publish reports and build estate snapshots. - Hyperscaler discovery servers extended in place; cloud-knowledge folded into them. - deploy/crucible-kab-dev.yaml: the Discovery package agent and the Assessment agents. - Platform issue write-ups and current-wiring notes under docs/platform-issues/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
MCP servers
| Server | Port | What it does | Credential |
|---|---|---|---|
azure-discovery |
8111 | Read-only discovery of an Azure estate, and Azure Well-Architected guidance | 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, and Google Cloud Well-Architected guidance | The customer's, per project |
alz-discovery-sample |
8110 | The Meridian sample estate, for evals | None |
Customers grant access as described in docs/customer-cloud-access.md.
Well-Architected guidance is a tool on each provider's own server (azure_search_well_architected,
gcp_search_well_architected), on the same connection. aws-discovery has none yet. A separate cloud-knowledge
server, on Kyndryl's own keys, was retired on 2026-11-04. A GCP search is billed to the connection's project, so that
project needs the Developer Knowledge API enabled and the identity needs serviceusage.services.use.
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 |
_common/test_knowledge.py |
The guidance tool's rules, on every server that offers it |
<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.
- 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.