Skip to content

Commit 7e4ab91

Browse files
kentcdoddskentcdodds
committed
chore: update video links in README files for exercises
1 parent 3644d8d commit 7e4ab91

File tree

13 files changed

+26
-0
lines changed

13 files changed

+26
-0
lines changed

‎exercises/01.ping/01.problem.connect/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Ping
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/01-ping-01-problem-connect-z2r7d" />
4+
35
👨‍💼 Let's get our MCP server running. The TypeScript SDK for MCP supports `ping`
46
out of the box, so all we need to do is initialize the server, set up a
57
transport for it, and then it should respond to `ping` requests.

‎exercises/01.ping/01.solution.connect/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Ping
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/01-ping-01-problem-connect-z2r7d/solution" />
4+
35
👨‍💼 Great job! Now we know we've got an MCP server up and running. From here we
46
can start adding a bunch of different tools, resources, and more to it.
57

‎exercises/01.ping/FINISHED.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
11
# Ping
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/01-ping-99-break-1jaat" />
4+
35
Great job! Let's keep moving!

‎exercises/01.ping/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Ping
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro-xh5mj" />
4+
35
The Model Context Protocol requires a few things:
46

57
1. A client that can send standardized requests to the server

‎exercises/02.tools/01.problem.simple/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Simple Tool
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/02-tools-01-problem-simple-f8kip" />
4+
35
👨‍💼 Let's get your MCP server ready to support tools! In this step, you'll:
46

57
- Declare the `tools` capability on your server.

‎exercises/02.tools/01.solution.simple/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Simple Tool
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/02-tools-01-problem-simple-f8kip/solution" />
4+
35
👨‍💼 Great job! You've just enabled tool support in your MCP server and registered
46
your very first tool. This is a foundational step—now your server can expose
57
functionality to clients in a standardized, discoverable way.

‎exercises/02.tools/02.problem.args/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Arguments
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/02-tools-02-problem-args-arrgc" />
4+
35
👨‍💼 Time to make your tool dynamic! In this step, you'll:
46

57
- Update your `add` tool to accept two arguments: `firstNumber` and

‎exercises/02.tools/02.solution.args/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Arguments
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/02-tools-02-problem-args-arrgc/solution" />
4+
35
👨‍💼 Well done! You've just made your MCP tool dynamic—now it can accept arguments
46
from the client and return results based on user input. This is a huge step
57
toward building truly interactive and useful AI-powered systems.

‎exercises/02.tools/03.problem.errors/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Error Handling
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/02-tools-03-problem-errors-e4r63" />
4+
35
👨‍💼 As we add more features, it's inevitable that things will sometimes go
46
wrong—maybe a user tries to get information that doesn't exist, or there's
57
a problem saving data. It's important that both users and LLMs get clear,

‎exercises/02.tools/03.solution.errors/README.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Error Handling
22

3+
<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/02-tools-03-problem-errors-e4r63/solution" />
4+
35
👨‍💼 Nicely done! Now, when something goes wrong, LLMs get a clear, structured
46
error message which they can use to generate a proper message for the end user.
57
This makes the app much more robust and user-friendly, and helps everyone know

0 commit comments

Comments
 (0)