Foundations
Build the first useful version on a real piece of work.
ORCHESTRATE / OPERATOR
Connect AI to the Real World with MCP
Build an MCP server that gives an AI client useful, bounded access to real tools and information without handing the model unrestricted application authority. Start from one job, expose the minimum capability, secure the connection and test the protocol as a product boundary.
Deep diveProven in the LabHands on
Builders connecting AI clients to internal tools or servicesOperators who understand workflows but need a practical MCP mental modelDevelopers who want a controlled protocol layer rather than one-off tool integrations
Advanced Pack
Turn it into a repeatable system with deeper implementation, reusable assets and harder operating decisions. Free during Early Access.
Final Lab
Test the capability in a practical scenario when you want another round.
YOU'LL LEAVE WITH
A result you can take back to real work.
A working MCP integration with bounded tools/resources, application-owned authorization, explicit side-effect rules and protocol/client acceptance evidence.
Expose one useful capability through MCP
Choose a real job, separate tools/resources, implement one bounded capability and prove a compatible client can discover/use it without embedding application authority in prompt text.
Make the MCP boundary secure and production-shaped
Add auth/authorization, scope, validation, side-effect controls, current protocol handling, error semantics, observability, rate limits and acceptance across supported client behavior.
WHAT ADVANCED ADDS
Take the method back to real work.
Advanced includes reusable artifacts, decision rules and implementation material designed to keep working after you close the Path.
MCP Capability Brief
A job-first design for which tools/resources the server exposes, what inputs they accept, what authority they have and what should remain outside MCP.
Tool Authority Matrix
A classification of read, prepare, decide and external side-effect tools with authentication, authorization and human approval requirements.
Protocol Acceptance Pack
A practical set of discovery/call/auth/error tests tied to the supported MCP protocol era and exact server version.
PATH MAP
Build the first version. Then make it operational.
Foundations takes you through the first useful result. Advanced adds the implementation depth, harder cases and operating discipline needed to reuse it.
- 01Choose the Job Before the ProtocolFree
- 02Separate Tools from Readable ContextFree
- 03Design One Bounded CapabilityFree
- 04Implement the Small MCP ServerFree
- 05Test the Client FlowFree
- 01Design Authentication and AuthorizationAdvanced
- 02Govern Side EffectsAdvanced
- 03Support the Current Protocol ContractAdvanced
- 04Validate, Meter and Rate LimitAdvanced
- 05Observe MCP Use Without Logging SecretsAdvanced
- 06Run Protocol AcceptanceAdvanced
The Overpowered MCP Server
A server exposes useful data but also broad write tools, weak token scope and unclear side effects. Reduce capability to the job, fix the authority boundary and prove the client can still complete the workflow.
Complete Advanced, take on the scenario if you want to test the capability, and pass it to create a lightweight shareable record of the result.
How Lab Achievements work →BEGIN THE PATH
Start with a real result.
Sign in with email and work through Foundations for free. Complete Foundations and unlock Advanced free during Early Access.
Start Foundations free