MCP Playbooks

Playbooks · MCP overview · Manifest registry →

Implementation guides for G.A.I.N MCP. The MCP Blueprint is the reference design for MCP as transport. The tool contract (what the LLM may propose) lives in the Agents Blueprint under Manifests. How-to: Agents: Manifests. MCP is one way to expose those tools, not the catalog.

PEP still gates every tool side effect. Enforcement lives in Runtime.

THE CLAIM

MCP is a governed capability surface, not the tool allowlist. The pinned manifest is the contract. MCP, OpenAPI, and domain APIs are adapters.

Where to go

Need	Start here
Tool schema, pdp_action, unknown-tool reject	Manifest registry
Version, pin, promote, roll back	Manifest lifecycle
MCP principles	G.A.I.N MCP
MCP reference design (transport)	MCP Blueprint
Manifest design (pinned tools)	Agents Blueprint
PEP maps pdp_action	Runtime
Schema and allowlist eval	Eval Plane ⑤ Tool

Recommended path

1. Manifest registry: contract shape (transport-agnostic)
2. Manifest lifecycle: storage and pin
3. G.A.I.N MCP and MCP Blueprint when MCP is the adapter
4. Runtime: PEP maps pdp_action to a verdict

Read next

Manifest registry →