fix slug

kentcdodds · kentcdodds · commit 06b487d797aa · 2025-09-24T15:41:54.000-06:00
diff --git a/exercises/01.advanced-tools/01.problem.annotations/README.mdx b/exercises/01.advanced-tools/01.problem.annotations/README.mdx
@@ -1,6 +1,6 @@
 # Annotations
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/annotations~n6qo2" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/annotations~n6qo2" />
 
 👨‍💼 Users want to feel confident about what each tool in the system does before they use it. They want to know if a tool is safe, if it will change their data, or if it might reach out to the outside world. When tools are clearly labeled for their behavior, the app feels more transparent and trustworthy.
 
diff --git a/exercises/01.advanced-tools/01.solution.annotations/README.mdx b/exercises/01.advanced-tools/01.solution.annotations/README.mdx
@@ -1,6 +1,6 @@
 # Annotations
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/annotations~n6qo2/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/annotations~n6qo2/solution" />
 
 👨‍💼 Fantastic progress! We've successfully introduced annotations to our journaling tools. Now, each tool clearly communicates its intent—whether it's read-only, destructive, idempotent, or open world. This means users and the system can better understand the impact of each action, leading to a safer and more predictable journaling experience. For example, deleting an entry is now marked as idempotent, while creating a tag is clearly non-destructive. These improvements help ensure that users can confidently manage their journal and tags, knowing exactly what each tool is designed to do.
 
diff --git a/exercises/01.advanced-tools/02.problem.structured/README.mdx b/exercises/01.advanced-tools/02.problem.structured/README.mdx
@@ -1,6 +1,6 @@
 # Structured Output
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/structured-output~egacc" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/structured-output~egacc" />
 
 👨‍💼 When users open EpicMe, they expect their memories, reflections, and daily adventures to be organized, discoverable, and (most importantly) reliable. Imagine a user writing a heartfelt entry about their day, only to have it saved as a jumbled scroll of text! That would be chaos in their personal archive.
 
diff --git a/exercises/01.advanced-tools/02.solution.structured/README.mdx b/exercises/01.advanced-tools/02.solution.structured/README.mdx
@@ -1,6 +1,6 @@
 # Structured Output
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/structured-output~egacc/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/structured-output~egacc/solution" />
 
 👨‍💼 Outstanding achievement! We've now brought structured output to our journaling tools, ensuring every action in EpicMe returns information in a clear, machine-validated format. This means users can trust that their memories, reflections, and daily adventures are always organized and reliably presented—no more cryptic or unpredictable responses. The UI can now display journal entries, tags, and magical creatures (😉) with confidence, knowing exactly what to expect from each tool. This upgrade not only makes the experience more seamless and delightful for our users, but also paves the way for smarter automation and safer interactions throughout the app.
 
diff --git a/exercises/01.advanced-tools/FINISHED.mdx b/exercises/01.advanced-tools/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Advanced Tools
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/break~70afq" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/break~70afq" />
 
 Awesome work. You now understand about annotations, structured output, and output schemas. Hopefully this enables you to take advantage of great client features when clients support these features.
diff --git a/exercises/01.advanced-tools/README.mdx b/exercises/01.advanced-tools/README.mdx
@@ -1,6 +1,6 @@
 # Advanced Tools
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/intro~2nnka" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/intro~2nnka" />
 
 ## Tool Annotations
 
diff --git a/exercises/02.elicitation/01.problem/README.mdx b/exercises/02.elicitation/01.problem/README.mdx
@@ -1,6 +1,6 @@
 # Elicit Confirmation
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/elicit-confirmation~oaha2" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/elicit-confirmation~oaha2" />
 
 👨‍💼 When users interact with our system, they sometimes initiate actions that have significant consequences (like deleting a tag or entry). To ensure users don't accidentally lose something important, we need to pause and ask for explicit confirmation before proceeding.
 
diff --git a/exercises/02.elicitation/01.solution/README.mdx b/exercises/02.elicitation/01.solution/README.mdx
@@ -1,6 +1,6 @@
 # Elicit Confirmation
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/elicit-confirmation~oaha2/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/elicit-confirmation~oaha2/solution" />
 
 👨‍💼 Fantastic progress! We've just introduced a robust confirmation step for destructive actions, such as deleting a tag. Now, whenever a user initiates an action that could have significant consequences, the system pauses and asks for explicit confirmation using a structured elicitation prompt. This ensures that users are always in control and never accidentally lose important data.
 
diff --git a/exercises/02.elicitation/FINISHED.mdx b/exercises/02.elicitation/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Elicitation
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/break~pa6st" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/break~pa6st" />
 
 Awesome job! You now know how to elicit input from the user while your tools are running, making your MCP server user experience that much better.
diff --git a/exercises/02.elicitation/README.mdx b/exercises/02.elicitation/README.mdx
@@ -1,6 +1,6 @@
 # Elicitation
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/intro~gs3h2" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/intro~gs3h2" />
 
 Modern AI applications often need to collect structured input from users at key moments in a workflow. **Elicitation** in the Model Context Protocol (MCP) standardizes this process, allowing servers to request information from users through the client, using a well-defined schema and a secure, user-friendly interaction model.
 
diff --git a/exercises/03.sampling/01.problem.simple/README.mdx b/exercises/03.sampling/01.problem.simple/README.mdx
@@ -1,6 +1,6 @@
 # Simple Sampling
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/simple-sampling~5yj44" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/simple-sampling~5yj44" />
 
 👨‍💼 Our users love the prompt functionality, but they asked why the LLM couldn't
 just suggest tags when they create the post and we thought that's a great idea!
diff --git a/exercises/03.sampling/01.solution.simple/README.mdx b/exercises/03.sampling/01.solution.simple/README.mdx
@@ -1,6 +1,6 @@
 # Simple Sampling
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/simple-sampling~5yj44/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/simple-sampling~5yj44/solution" />
 
 👨‍💼 Great! Now we're wired up to ask the LLM to do stuff for us. Let's get to
 that next.
diff --git a/exercises/03.sampling/02.problem.advanced/README.mdx b/exercises/03.sampling/02.problem.advanced/README.mdx
@@ -1,6 +1,6 @@
 # Advanced Sampling Prompt
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/advanced-sampling-prompt~qyf7c" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/advanced-sampling-prompt~qyf7c" />
 
 👨‍💼 Now that you've wired up basic sampling, it's time to make your prompt
 have the LLM do something actually useful! Instead of just asking for a generic
diff --git a/exercises/03.sampling/02.solution.advanced/README.mdx b/exercises/03.sampling/02.solution.advanced/README.mdx
@@ -1,6 +1,6 @@
 # Advanced Sampling Prompt
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/advanced-sampling-prompt~qyf7c/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/advanced-sampling-prompt~qyf7c/solution" />
 
 👨‍💼 Hooray! Now our users can get tag suggestions from the LLM when they create a
 new journal entry and have those actually be created and applied! Cool!
diff --git a/exercises/03.sampling/FINISHED.mdx b/exercises/03.sampling/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Sampling
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/break~iezdw" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/break~iezdw" />
 
 Great! Our users are happy with the sampling functionality you've
 implemented. It's really turning their assistant into an actual assistant!
diff --git a/exercises/03.sampling/README.mdx b/exercises/03.sampling/README.mdx
@@ -1,6 +1,6 @@
 # Sampling
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/intro~0dyu8" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/intro~0dyu8" />
 
 Modern AI applications often need to generate new content (whether that's text,
 images, or more) on demand. This process is called **sampling**: asking a
diff --git a/exercises/04.long-running-tasks/01.problem.progress/README.mdx b/exercises/04.long-running-tasks/01.problem.progress/README.mdx
@@ -1,6 +1,6 @@
 # Progress Updates
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/progress-updates~a3g0l" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/progress-updates~a3g0l" />
 
 👨‍💼 When users ask our mcp server to generate their journal wrapped video, it can take some time and they want to know that things are moving along. Nobody likes staring at a blank screen, wondering if the app is frozen or if their request was even received. Progress updates are how we keep users in the loop, making the wait feel shorter and the experience more delightful.
 
diff --git a/exercises/04.long-running-tasks/01.solution.progress/README.mdx b/exercises/04.long-running-tasks/01.solution.progress/README.mdx
@@ -1,6 +1,6 @@
 # Progress Updates
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/progress-updates~a3g0l/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/progress-updates~a3g0l/solution" />
 
 👨‍💼 Fantastic news! We've just made waiting for a journal wrapped video a much better experience. Now, when users request their video, they receive real-time progress updates throughout the process. Instead of staring at a blank screen and wondering if anything is happening, users see clear, friendly notifications that keep them in the loop from start to finish.
 
diff --git a/exercises/04.long-running-tasks/02.problem.cancellation/README.mdx b/exercises/04.long-running-tasks/02.problem.cancellation/README.mdx
@@ -1,6 +1,6 @@
 # Cancellation
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/cancellation~6o5mm" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/cancellation~6o5mm" />
 
 👨‍💼 When users embark on creating their personalized wrapped video, the process can take a while (especially if they journal a lot). Sometimes, halfway through, they realize they picked the wrong year, or maybe their cat walks across the keyboard and they want to stop the operation immediately. It's essential that our app gives users the power to cancel these long-running tasks, so they always feel in control and never stuck waiting for something they no longer want.
 
diff --git a/exercises/04.long-running-tasks/02.solution.cancellation/README.mdx b/exercises/04.long-running-tasks/02.solution.cancellation/README.mdx
@@ -1,6 +1,6 @@
 # Cancellation
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/cancellation~6o5mm/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/cancellation~6o5mm/solution" />
 
 👨‍💼 Outstanding progress! We've just empowered our users with the ability to cancel long-running operations—like generating their personalized wrapped video—at any time. This means that if a user changes their mind, makes a mistake, or simply needs to stop the process, they can do so instantly, without waiting for the task to finish.
 
diff --git a/exercises/04.long-running-tasks/FINISHED.mdx b/exercises/04.long-running-tasks/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Long Running Tasks
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/break~j3a9t" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/break~j3a9t" />
 
 You can now manage long-running tasks in your tools, reporting progress and allowing users to cancel operations. Good job!
diff --git a/exercises/04.long-running-tasks/README.mdx b/exercises/04.long-running-tasks/README.mdx
@@ -1,6 +1,6 @@
 # Long Running Tasks
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/intro~wjyc8" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/intro~wjyc8" />
 
 In this exercise, you'll learn how to handle long-running tasks in the context of the Model Context Protocol (MCP), with a focus on **progress reporting** and **cancellation**. (As a bonus, you'll also get hands-on experience with JavaScript's `AbortController` and signals, which are essential for managing asynchronous operations that can be cancelled).
 
diff --git a/exercises/05.changes/01.problem.list-changed/README.mdx b/exercises/05.changes/01.problem.list-changed/README.mdx
@@ -1,6 +1,6 @@
 # List Changed
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/list-changed~43sfe" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/list-changed~43sfe" />
 
 👨‍💼 When people use the Epic Me journal app, they expect the interface to always reflect what's possible right now. If a new journaling prompt becomes available, or a feature is temporarily disabled, users want the UI to update instantly. No confusion, no stale buttons, just a smooth, up-to-date experience.
 
diff --git a/exercises/05.changes/01.solution.list-changed/README.mdx b/exercises/05.changes/01.solution.list-changed/README.mdx
@@ -1,6 +1,6 @@
 # List Changed
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/list-changed~43sfe/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/list-changed~43sfe/solution" />
 
 👨‍💼 Fantastic progress! Our app now supports real-time updates for journaling
 prompts, thanks to the new `list_changed` notification capability. Whenever a
diff --git a/exercises/05.changes/02.problem.resources-list-changed/README.mdx b/exercises/05.changes/02.problem.resources-list-changed/README.mdx
@@ -1,6 +1,6 @@
 # Resource Template List Changed
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/resource-template-list-changed~lkds0" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/resource-template-list-changed~lkds0" />
 
 👨‍💼 When people use our EpicMe journaling app, they expect the list of available resources (like journal entries, tags, or even videos) to always reflect what's actually possible right now. Imagine a user just added a new video reflection or created a fresh tag for their latest entry. They want to see those options appear instantly, without needing to refresh or wonder if something is out of sync.
 
diff --git a/exercises/05.changes/02.solution.resources-list-changed/README.mdx b/exercises/05.changes/02.solution.resources-list-changed/README.mdx
@@ -1,6 +1,6 @@
 # Resource Template List Changed
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/resource-template-list-changed~lkds0/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/resource-template-list-changed~lkds0/solution" />
 
 👨‍💼 Outstanding work! Our app now keeps the list of available resources—like journal entries, tags, and videos—perfectly in sync with what's actually possible for the user, thanks to the new `list_changed` notification for resource templates. Now, whenever a user adds a new video reflection, creates a fresh tag, or updates their journal, the UI updates instantly.
 
diff --git a/exercises/05.changes/03.problem.subscriptions/README.mdx b/exercises/05.changes/03.problem.subscriptions/README.mdx
@@ -1,6 +1,6 @@
 # Subscriptions
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/subscriptions~hja2q" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/subscriptions~hja2q" />
 
 👨‍💼 When people use our EpicMe journaling MCP, they want the LLM they're using to always have the latest version of their jounraling data. Exposing subscriptions for resources (like a particular entry, tag, or video) allows clients to be notified of changes to specific resources the LLM is using in its context or the client may be using for other purposes.
 
diff --git a/exercises/05.changes/03.solution.subscriptions/README.mdx b/exercises/05.changes/03.solution.subscriptions/README.mdx
@@ -1,6 +1,6 @@
 # Subscriptions
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/subscriptions~hja2q/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/subscriptions~hja2q/solution" />
 
 👨‍💼 Way to go! We've just unlocked real-time updates for our users by enabling resource subscriptions. Now, whenever someone is working with a specific journal entry, tag, or video, the app can instantly notify them of any changes—no more stale data or manual refreshes. This means users always have the most up-to-date information at their fingertips, making their journaling experience seamless and trustworthy.
 
diff --git a/exercises/05.changes/FINISHED.mdx b/exercises/05.changes/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Changes
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/break~yv13f" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/break~yv13f" />
 
 Great job on this exercise. You now know how to make dynamic MCP servers.
diff --git a/exercises/05.changes/README.mdx b/exercises/05.changes/README.mdx
@@ -1,6 +1,6 @@
 # Changes
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/intro~s3qik" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/intro~s3qik" />
 
 In a web application, the buttons, links, and data that you see change based on the context. Whether the user is currently logged in, whether there is any data available, what role the user has, etc. MCP servers are no different. The information and tools they provide can change at any time.
 
diff --git a/exercises/FINISHED.mdx b/exercises/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Advanced MCP Features 🐡
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/outro-you-ve-finished-advanced-mcp~ly753" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/outro-you-ve-finished-advanced-mcp~ly753" />
 
 You made it all the way through! This workshop took you beyond the fundamentals and into the capabilities that make MCP servers powerful, adaptable, and genuinely helpful in real-world AI-assisted workflows.
 
diff --git a/exercises/README.mdx b/exercises/README.mdx
@@ -1,6 +1,6 @@
 # Advanced MCP Features 🐡
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-3-advanced-tools-sampling-and-elicitation/intro-learn-advanced-features-for-better-ux~zuzak" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-3-4-advanced-mcp-features/intro-learn-advanced-features-for-better-ux~zuzak" />
 
 👨‍💼 Hello, my name is Peter the Product Manager. I'm here to help you get
 oriented and to give you your assignments for the workshop!
diff --git a/package.json b/package.json
@@ -18,7 +18,7 @@
     },
     "product": {
       "host": "www.epicai.pro",
-      "slug": "day-3-advanced-tools-sampling-and-elicitation",
+      "slug": "day-3-4-advanced-mcp-features",
       "displayName": "EpicAI.pro",
       "displayNameShort": "Epic AI",
       "discordChannelId": "1409600723716411494",
