learn mcp with phoebe - a two-track course on the Model Context Protocol

The leader track 🤝 · for C-level, managers & curious minds · 6 x 45 min · no code to write

Thinking mode: why MCP exists, what it changes for your integration budget, how to question vendors on security, and what the 2026 roadmap means for strategy - each session ends with questions to ask your teams.

🔌 Leader 1 · easy

Why MCP exists

The N x M integration problem, the USB-C move that collapsed it, and why every major AI vendor signed on within a year.

▶ Leaders start here 🏛️ Leader 2 · easy

The architecture in plain English

Host, client, server without jargon - and what tools, resources, and prompts mean as business capabilities you can commission.

No-code session 🌐 Leader 3 · medium

The ecosystem play

The official registry, ~97M monthly SDK downloads, who adopted what - and the build vs buy vs wait decision for your org.

Build-vs-buy exercise 🛡️ Leader 4 · medium

Security and trust

What an MCP server can actually reach, OAuth in plain terms, the real risk register, and the questions that expose a weak vendor.

Vendor-grilling checklist 🏢 Leader 5 · deciding

MCP in your organization

Scanning your org for MCP-shaped wins, connector strategy, governance scopes, and how to frame the ROI to a board.

Use-case scan exercise 🔭 Leader 6 · deciding

The roadmap and your strategy

The 2026-07-28 spec revision, MCP Apps, tasks, extensions, deprecations - what changes, what to fund, what to wait on.

Strategy session

The builder track 🛠️ · for practitioners · 8 x 45 min · Python · live wire inspector on every page

One running project, built harder every session: the Daybreak MCP server - tools over real sales data, resources, prompts, then a client, remote deployment, OAuth, and a registry listing. Spec 2025-11-25, with every 2026-07-28 change flagged where it bites.

📡 Builder 1 · easy

What MCP actually is

Host / client / server, all six primitives, and the JSON-RPC wire itself - stepped through message by message, live.

▶ Builders start here ⚙️ Builder 2 · easy

Your first MCP server

Python SDK, FastMCP, three real tools over Daybreak's data, and the MCP Inspector to poke them - from zero to working server.

Ship tools tonight 📚 Builder 3 · medium

Resources and prompts

Complete the server trio: the menu and policies as resources, a daily-report prompt, completion and pagination as they arise.

Context + playbooks 🔗 Builder 4 · medium

Connect to real hosts

Daybreak inside Claude Code and Claude Desktop: .mcp.json, local / project / user scopes, env vars, and reference servers.

Your server, real apps 🤖 Builder 5 · medium

Build a client

The other side of the wire: a Python client and a chatbot that discovers and calls Daybreak's tools - Claude API or local Ollama.

Dual Claude/Ollama path ☁️ Builder 6 · hands-on

Remote servers

Streamable HTTP in depth, state, deployment, and the MCP connector - calling your server straight from the Messages API.

stdio to production 🔐 Builder 7 · hands-on

Auth, security, elicitation

OAuth 2.1 as MCP does it, the security best practices that matter, and elicitation - the server asking your user mid-task.

The open lane 🚀 Builder 8 · hardest

Registry and what's next

Publish Daybreak to the official registry, versioning, then the 2026-07-28 delta in full: stateless core, MCP Apps, tasks, deprecations.

Ship + future-proof

easy - everyone medium hands-on / deciding hardest

Choose your path 🗺️

Two doors, one protocol. Leaders never touch code; builders never sit through strategy they have not just wired themselves.

🤝 Leader (judge & govern) a1→ a2→ a3→ a4→ a5→ a6

🛠️ Builder (ship Daybreak) b1→ b2→ b3→ b4→ b5→ b6→ b7→ b8

🌱 Curious follower (a taste) a1→ a2→ b1

🚀 Full journey (lead AND build) a1-a6→ b1-b8

The knowledge map 🧠

Both tracks at a glance - hover a session to spotlight its concepts, click any node to jump in.