Rich MCP clients can use prompts, resources, image blocks, and OAuth discovery. Basic clients support only tool calls. A well-designed MCP server should use all of these when available but never depend on a rich client for the core experience. This talk introduces the capability cascade pattern: skills entries become MCP prompts for clients that support them, entries can become MCP resources for resource-capable clients, image artifacts return native image blocks when possible, and read tool with view parameters provides a universal tool-based fallback for everything. We demonstrate the same data served five different ways to five different clients, showing how the server adapts without separate codepaths.