[Intro] (dusty vinyl crackle, warm Rhodes chord) (four pieces, one map...) [Verse 1] You read the blueprint, see four names in a row, and you ask, "which one wins? which one do I go?" But that's the trap, friend, that's where folks fall — they treat 'em as rivals, but they layer, that's all. A real support agent uses several at once, so "which is best?" is the wrong kind of hunt. [Pre-Chorus] (build) Don't pick a winner — place where it lives, which layer owns the problem the scenario gives. [Chorus] (drop) Four technologies, one composed stack! Author some, deploy the rest — and you won't look back. (oh-oh) API, SDK, Claude Code, MCP — not four ways to do one thing, they're a family. (one stack!) [Verse 2] Down at the base the API holds the floor, it forgets every turn, so you send it once more. You build a loop yourself if you're raw on the wire, 'cause the model asks for tools — but it can't pull the trigger. Climb a layer up, let the SDK drive, and Claude Code's the agent you deploy live. [Verse - Rap] (half-time, confident) Stateless base: the Messages endpoint, no memory kept, resend the whole conversation, every result you've collected; declare your tools as schemas, the model picks the call, emits a structured request — your code runs it, that's all. SDK sits one above, runs the loop in your place, spawns subagents, fresh context, scoped tools, own space; and it exposes hooks — that deterministic seam, where plain code blocks or validates the probabilistic machine. Claude Code? Ready-made agent, you deploy and you tune: CLAUDE.md, skills, slash commands, plan mode in the room. MCP's the open protocol — not a model, not a brand — tools, resources, prompts: integrate once, reuse on demand. [Chorus] (drop) Four technologies, one composed stack! Author some, deploy the rest — and you won't look back. (oh-oh) API, SDK, Claude Code, MCP — not four ways to do one thing, they're a family. (one stack!) [Bridge] (half-time, low) Don't conflate the SDK with Claude Code, they split clean: "build my own agent" versus "deploy the coding machine." And MCP ain't the model — it's the wire in between; the model never runs the tool, it just calls the routine. [Final Chorus] (full drop) Four technologies, one composed stack! (one map!) Author some, deploy the rest — and you won't look back. API, SDK, Claude Code, MCP — place the scenario on the map, and the answer's what you see! (one stack!) [Outro — call to action] (spoken over the final fade) Want the deep version? Get *The CCA-F Study Guide* on Leanpub — leanpub.com/cca-f (...one composed stack)
