Production-shaped MCP setups, each drawn twice: the numbered flow (what
happens) and the sequence diagram (who says what to whom, in order). Every one is
lesson 04's seven messages, repeated — read one wire, read them all. Companion to
lesson 08.
1 🐙 The coding assistant — IDE + GitHub + files
“Fix issue #42.” Read the complaint, read the code, run the tests, draft the PR — and the PR waits for a human click.
The flow, numbered:
The sequence, message by message:
💡 Why MCP here: the same GitHub server works in every IDE and agent — write once, plug in everywhere (L01's N+M).
2 🎧 The support desk — orders DB + docs
“Where's my refund?” Look up the order (read-only), fetch the policy, answer with receipts.
The flow, numbered:
The sequence, message by message:
💡 Why MCP here: grounding beats guessing (AI course L09) — and the read-only scoped account makes the worst case boring.
3 📊 The data analyst — SQL + charts
“Which product sold best last month, per region?” Query, chart, explain — in the chat.
The flow, numbered:
The sequence, message by message:
💡 Why MCP here: one SQL server serves every team's AI app; schema design (L06) is the guardrail.