Every plugin that ships with MCPG — backends, identity providers, policy engines, tool-gates, transforms, observability sinks, payment rails, and infrastructure adapters — with its id, class, and what it does.

The 27 backend kinds MCPG ships — HTTP, command, NATS, gRPC, GraphQL, Kafka, SQL, OpenAPI, mock, pipeline, plus a 17-kind LLM family — each selected by a nested backend.kind discriminator on an MCP capability.

Every MCPG command-line tool — the gateway (mcpg), plugin artifacts (mcpg-plugins), the config tooling, the control-plane CLI (mcpg-ctl), the control-plane server, and the Kubernetes operator — and how they fit together.

Every MCPG gateway configuration key, generated from the live AppConfig schema. The gateway rejects unknown fields at boot, so this is the exact, complete surface.

The MCPG gateway binary — run it, configure it via MCPG_CONFIG, force the stdio transport, and use the dev / plugin front-door subcommands.

The seven standalone tools that scaffold, validate, document, and inspect the MCPG gateway AppConfig.

The MCPG control-plane REST/gRPC server that mcpg-ctl and gateway agents talk to — its flags, defaults, and secure-deployment notes.

The MCPG control-plane CLI — run the CP locally, enrol gateways, sign in via OIDC, and drive Cloud provisioning + cluster admin.

The MCPG Kubernetes operator that reconciles the mcpg.dev CRDs, plus crdgen for generating the CRD YAML.

Scaffold, hash, sign, pack, push, pull, and test MCPG plugin artifact files — invoked directly or via mcpg plugin <cmd>.

The eight mcpg.dev/v1alpha2 Custom Resource Definitions the MCPG Kubernetes operator reconciles — scope, key spec fields, and status, derived directly from the operator API types and the rendered CRDs.

The 18 pipeline step kinds — backend, composition, notification, SQL-container, and suspending — that compose multiple operations into a single MCP tool call, with data flow and client interaction.