From c3abf3b81ca775f42369206382d648e5ba849ce1 Mon Sep 17 00:00:00 2001 From: burtenshaw Date: Thu, 15 May 2025 14:37:09 +0200 Subject: [PATCH 1/2] update coming soon pages --- units/en/_toctree.yml | 4 ++-- units/en/unit3/introduction.mdx | 4 +++- units/en/unit4/introduction.mdx | 6 +++++- 3 files changed, 10 insertions(+), 4 deletions(-) diff --git a/units/en/_toctree.yml b/units/en/_toctree.yml index f916d54..275a478 100644 --- a/units/en/_toctree.yml +++ b/units/en/_toctree.yml @@ -38,9 +38,9 @@ - title: "3. Use Case: Advanced MCP Development" sections: - local: unit3/introduction - title: Introduction + title: Coming Soon - title: "Bonus Units" sections: - local: unit4/introduction - title: Introduction + title: Coming Soon diff --git a/units/en/unit3/introduction.mdx b/units/en/unit3/introduction.mdx index d1526ee..d3c9b29 100644 --- a/units/en/unit3/introduction.mdx +++ b/units/en/unit3/introduction.mdx @@ -1 +1,3 @@ -# Introduction \ No newline at end of file +# Coming Soon + +This will be another use case that dives deeper into the MCP protocol and how to use it in more complex ways. \ No newline at end of file diff --git a/units/en/unit4/introduction.mdx b/units/en/unit4/introduction.mdx index 67b7e26..5eed14d 100644 --- a/units/en/unit4/introduction.mdx +++ b/units/en/unit4/introduction.mdx @@ -1 +1,5 @@ -# Advanced Topics, Security, and the Future of MCP \ No newline at end of file +# Coming Soon + +This unit will be a collaboration with partners from the AI community. + +If you're building tools for MCP, please reach out to us and we'll add you to the unit. Open a [discussion](https://huggingface.co/spaces/mcp-course/README/discussions) on the hub organization. \ No newline at end of file From d1d07cac24fd6eb1b975ba70631f4ea9990219ae Mon Sep 17 00:00:00 2001 From: burtenshaw Date: Thu, 15 May 2025 14:45:29 +0200 Subject: [PATCH 2/2] use inline and table style for protocol diagram --- units/en/unit1/communication-protocol.mdx | 177 ++++++++-------------- 1 file changed, 63 insertions(+), 114 deletions(-) diff --git a/units/en/unit1/communication-protocol.mdx b/units/en/unit1/communication-protocol.mdx index 4c7ec96..a01afaf 100644 --- a/units/en/unit1/communication-protocol.mdx +++ b/units/en/unit1/communication-protocol.mdx @@ -129,73 +129,27 @@ In the previous section, we discussed the lifecycle of a single interaction betw The MCP protocol defines a structured interaction lifecycle between Clients and Servers: - - ### Initialization The Client connects to the Server and they exchange protocol versions and capabilities, and the Server responds with its supported protocol version and capabilities. -
-
💻
-
- initialize -
-
🌐
-
-
💻
-
- response -
-
🌐
-
-
💻
-
- initialized -
-
🌐
-
+ + + + + + + + + + + + + + + + +
💻
initialize
🌐
💻
response
🌐
💻
initialized
🌐
The Client confirms the initialization is complete via a notification message. @@ -203,19 +157,18 @@ The Client confirms the initialization is complete via a notification message. The Client requests information about available capabilities and the Server responds with a list of available tools. -
-
💻
-
- tools/list -
-
🌐
-
-
💻
-
- response -
-
🌐
-
+ + + + + + + + + + + +
💻
tools/list
🌐
💻
response
🌐
This process could be repeated for each tool, resource, or prompt type. @@ -223,49 +176,45 @@ This process could be repeated for each tool, resource, or prompt type. The Client invokes capabilities based on the Host's needs. -
-
💻
-
- tools/call -
-
🌐
-
-
💻
-
- notification (optional progress) -
-
🌐
-
-
💻
-
- response -
-
🌐
-
+ + + + + + + + + + + + + + + + +
💻
tools/call
🌐
💻
notification (optional progress)
🌐
💻
response
🌐
### Termination The connection is gracefully closed when no longer needed and the Server acknowledges the shutdown request. -
-
💻
-
- shutdown -
-
🌐
-
-
💻
-
- response -
-
🌐
-
-
💻
-
- exit -
-
🌐
-
+ + + + + + + + + + + + + + + + +
💻
shutdown
🌐
💻
response
🌐
💻
exit
🌐
The Client sends the final exit message to complete the termination.