Build client workflows with MCP
Combine discovery and capability calls while keeping the user in control.
- Explain how a host can use MCP capabilities in an assistant workflow.
An MCP host can discover server capabilities, provide suitable ones to a model, and route a selected tool call through the matching client. The host receives the result and decides how to present it or continue the workflow. The model may suggest a tool call, but the host remains responsible for user experience, policy, and handling the returned data.
A small example
1request = {"tool": "lookup_order", "arguments": {"order_id": "A-104"}}
2result = {"status": "shipped"}
3tool_name = request["tool"]
4status = result["status"]
5print(f"Call {tool_name}; show result: {status}")Call lookup_order; show result: shipped
Servers may offer additional features such as progress notifications, pagination, or resource updates. Clients should handle partial results, cancellation, and errors where supported. Do not assume that every server has every optional capability; discover and negotiate what is available.
Key takeaways
Explain how a host can use MCP capabilities in an assistant workflow.
Keep capability access explicit and handle results as untrusted input.
Lesson quiz
5 questions · pass with 4 correct · up to 50 XP
Passing this quiz completes the lesson and keeps your streak going. Questions you miss come back in review sessions later.
Questions about this lesson
Stuck? Ask. Figured something out? Share it. Explaining is one of the best ways to learn.
Loading posts…