update based on new slug

kentcdodds · kentcdodds · commit bf0ebd50f4d6 · 2025-09-24T15:37:09.000-06:00
diff --git a/exercises/01.ping/01.problem.connect/README.mdx b/exercises/01.ping/01.problem.connect/README.mdx
@@ -1,6 +1,6 @@
 # Ping
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/ping-connect~z2r7d" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/ping-connect~z2r7d" />
 
 👨‍💼 Let's get our MCP server running. The TypeScript SDK for MCP supports `ping`
 out of the box, so all we need to do is initialize the server, set up a
diff --git a/exercises/01.ping/01.solution.connect/README.mdx b/exercises/01.ping/01.solution.connect/README.mdx
@@ -1,6 +1,6 @@
 # Ping
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/ping-connect~z2r7d/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/ping-connect~z2r7d/solution" />
 
 👨‍💼 Great job! Now we know we've got an MCP server up and running. From here we
 can start adding a bunch of different tools, resources, and more to it.
diff --git a/exercises/01.ping/FINISHED.mdx b/exercises/01.ping/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Ping
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/break~1jaat" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/break~1jaat" />
 
 Great job! Let's keep moving!
diff --git a/exercises/01.ping/README.mdx b/exercises/01.ping/README.mdx
@@ -1,6 +1,6 @@
 # Ping
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro~xh5mj" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/intro~xh5mj" />
 
 The Model Context Protocol requires a few things:
 
diff --git a/exercises/02.tools/01.problem.simple/README.mdx b/exercises/02.tools/01.problem.simple/README.mdx
@@ -1,6 +1,6 @@
 # Simple Tool
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/simple-tool~f8kip" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/simple-tool~f8kip" />
 
 👨‍💼 Let's get your MCP server ready to support tools! In this step, you'll:
 
diff --git a/exercises/02.tools/01.solution.simple/README.mdx b/exercises/02.tools/01.solution.simple/README.mdx
@@ -1,6 +1,6 @@
 # Simple Tool
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/simple-tool~f8kip/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/simple-tool~f8kip/solution" />
 
 👨‍💼 Great job! You've just enabled tool support in your MCP server and registered
 your very first tool. This is a foundational step—now your server can expose
diff --git a/exercises/02.tools/02.problem.args/README.mdx b/exercises/02.tools/02.problem.args/README.mdx
@@ -1,6 +1,6 @@
 # Arguments
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/arguments~rosou" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/arguments~rosou" />
 
 👨‍💼 Time to make your tool dynamic! In this step, you'll:
 
diff --git a/exercises/02.tools/02.solution.args/README.mdx b/exercises/02.tools/02.solution.args/README.mdx
@@ -1,6 +1,6 @@
 # Arguments
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/arguments~rosou/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/arguments~rosou/solution" />
 
 👨‍💼 Well done! You've just made your MCP tool dynamic—now it can accept arguments
 from the client and return results based on user input. This is a huge step
diff --git a/exercises/02.tools/03.problem.errors/README.mdx b/exercises/02.tools/03.problem.errors/README.mdx
@@ -1,6 +1,6 @@
 # Error Handling
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/error-handling~mbnk6" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/error-handling~mbnk6" />
 
 👨‍💼 As we add more features, it's inevitable that things will sometimes go
 wrong—maybe a user tries to get information that doesn't exist, or there's
diff --git a/exercises/02.tools/03.solution.errors/README.mdx b/exercises/02.tools/03.solution.errors/README.mdx
@@ -1,6 +1,6 @@
 # Error Handling
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/error-handling~mbnk6/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/error-handling~mbnk6/solution" />
 
 👨‍💼 Nicely done! Now, when something goes wrong, LLMs get a clear, structured
 error message which they can use to generate a proper message for the end user.
diff --git a/exercises/02.tools/FINISHED.mdx b/exercises/02.tools/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Tools
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/break~fvaf4" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/break~fvaf4" />
 
 Great job! You've now built a server that can expose tools to clients, handle
 arguments, and return dynamic results. This is a huge leap toward building
diff --git a/exercises/02.tools/README.mdx b/exercises/02.tools/README.mdx
@@ -1,6 +1,6 @@
 # Tools
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro~r0cbh" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/intro~r0cbh" />
 
 The Model Context Protocol (MCP) enables language models to interact with
 external systems through a concept called "tools." Tools are server-defined
diff --git a/exercises/03.resources/01.problem.simple/README.mdx b/exercises/03.resources/01.problem.simple/README.mdx
@@ -1,6 +1,6 @@
 # Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resources~ah1hi" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resources~ah1hi" />
 
 👨‍💼 Our users really want to include their tags in the context as they write
 their journal entries. They could just ask the LLM to run the `list_tags` tool,
diff --git a/exercises/03.resources/01.solution.simple/README.mdx b/exercises/03.resources/01.solution.simple/README.mdx
@@ -1,6 +1,6 @@
 # Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resources~ah1hi/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resources~ah1hi/solution" />
 
 👨‍💼 Well done! You've just registered your very first MCP resource. Now your
 server can expose structured data—like credits, files, or database records—as
diff --git a/exercises/03.resources/02.problem.template/README.mdx b/exercises/03.resources/02.problem.template/README.mdx
@@ -1,6 +1,6 @@
 # Resource Templates
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resource-templates~4cwge" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resource-templates~4cwge" />
 
 👨‍💼 Now that you've registered a static resource, let's make things more dynamic!
 In this step, you'll use MCP's resource templates to expose a whole family of
diff --git a/exercises/03.resources/02.solution.template/README.mdx b/exercises/03.resources/02.solution.template/README.mdx
@@ -1,6 +1,6 @@
 # Resource Templates
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resource-templates~4cwge/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resource-templates~4cwge/solution" />
 
 👨‍💼 Fantastic work! You've just leveled up your MCP server by implementing
 dynamic resource templates. Now your server can expose entire collections of
diff --git a/exercises/03.resources/03.problem.list/README.mdx b/exercises/03.resources/03.problem.list/README.mdx
@@ -1,6 +1,6 @@
 # Resource Templates List
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resource-templates-list~5v3h2" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resource-templates-list~5v3h2" />
 
 👨‍💼 Our users want to be able to see a list of all tags. So let's implement the
 `list` callback for our resource templates.
diff --git a/exercises/03.resources/03.solution.list/README.mdx b/exercises/03.resources/03.solution.list/README.mdx
@@ -1,5 +1,5 @@
 # Resource Templates List
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resource-templates-list~5v3h2/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resource-templates-list~5v3h2/solution" />
 
 👨‍💼 Great! Now clients can get a list of all entries and tags.
diff --git a/exercises/03.resources/04.problem.completion/README.mdx b/exercises/03.resources/04.problem.completion/README.mdx
@@ -1,6 +1,6 @@
 # Resource Template Completions
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resource-template-completions~2wp57" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resource-template-completions~2wp57" />
 
 👨‍💼 Now that our users have a bunch of entries and tags, they'll want to be able
 to search for them. Let's add some completions to our resource templates to
diff --git a/exercises/03.resources/04.solution.completion/README.mdx b/exercises/03.resources/04.solution.completion/README.mdx
@@ -1,6 +1,6 @@
 # Resource Template Completions
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/resource-template-completions~2wp57/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/resource-template-completions~2wp57/solution" />
 
 👨‍💼 Great! That's a much better experience for our users who will be trying to
 select the appropriate resource for their task.
diff --git a/exercises/03.resources/FINISHED.mdx b/exercises/03.resources/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/break~n1ttg" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/break~n1ttg" />
 
 Congratulations! You've mastered MCP resources—making your server capable of
 exposing, listing, and embedding structured data for clients and LLMs. From
diff --git a/exercises/03.resources/README.mdx b/exercises/03.resources/README.mdx
@@ -1,6 +1,6 @@
 # Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro~xrkgx" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/intro~xrkgx" />
 
 In previous exercises, you learned how to extend your MCP server with
 tools—server-defined functions that let clients perform actions or retrieve
diff --git a/exercises/04.resource-tools/01.problem.embedded/README.mdx b/exercises/04.resource-tools/01.problem.embedded/README.mdx
@@ -1,6 +1,6 @@
 # Embedded Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/embedded-resources~07e0z" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/embedded-resources~07e0z" />
 
 👨‍💼 Right now we have a `get_entry` tool that returns a journal entry. So LLMs
 can decide to get the entry details if it's relevant to the task. We also have
diff --git a/exercises/04.resource-tools/01.solution.embedded/README.mdx b/exercises/04.resource-tools/01.solution.embedded/README.mdx
@@ -1,6 +1,6 @@
 # Embedded Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/embedded-resources~07e0z/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/embedded-resources~07e0z/solution" />
 
 👨‍💼 Great! Now the LLM can still get the full details of a journal entry and the
 client can use the information from the resource to subscribe to the URI or
diff --git a/exercises/04.resource-tools/02.problem.linked/README.mdx b/exercises/04.resource-tools/02.problem.linked/README.mdx
@@ -1,6 +1,6 @@
 # Linked Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/linked-resources~j6z37" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/linked-resources~j6z37" />
 
 👨‍💼 You've already made your resources discoverable and accessible—now let's make
 them even more useful! In this step, you'll learn how to link a resource
diff --git a/exercises/04.resource-tools/02.solution.linked/README.mdx b/exercises/04.resource-tools/02.solution.linked/README.mdx
@@ -1,6 +1,6 @@
 # Linked Resources
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/linked-resources~j6z37/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/linked-resources~j6z37/solution" />
 
 👨‍💼 Brilliant work! You've just unlocked a new level of interactivity by
 linking to resources directly in your tool responses. Now your tools and
diff --git a/exercises/04.resource-tools/FINISHED.mdx b/exercises/04.resource-tools/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Resources in Tools
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/break~m2vj0" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/break~m2vj0" />
 
 Great work! You now know how to embed and link resources in tool responses.
diff --git a/exercises/04.resource-tools/README.mdx b/exercises/04.resource-tools/README.mdx
@@ -1,6 +1,6 @@
 # Resources in Tools
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro~ezvmy" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/intro~ezvmy" />
 
 In the previous exercise, you learned how to expose structured data (like journal entries and tags) as **resources** using the Model Context Protocol (MCP). You registered resources, made them discoverable, and enabled clients to list and read them by URI.
 
diff --git a/exercises/05.prompts/01.problem.prompts/README.mdx b/exercises/05.prompts/01.problem.prompts/README.mdx
@@ -1,6 +1,6 @@
 # Prompts
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/prompts~qyv9r" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/prompts~qyv9r" />
 
 👨‍💼 Let's make it easier for users to get helpful suggestions in your journaling
 app—without having to write their own prompts from scratch every time.
diff --git a/exercises/05.prompts/01.solution.prompts/README.mdx b/exercises/05.prompts/01.solution.prompts/README.mdx
@@ -1,6 +1,6 @@
 # Prompts
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/prompts~qyv9r/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/prompts~qyv9r/solution" />
 
 👨‍💼 You're doing awesome! Adding prompt support is a nice quality of life
 improvement for your users.
diff --git a/exercises/05.prompts/02.problem.optimized-prompt/README.mdx b/exercises/05.prompts/02.problem.optimized-prompt/README.mdx
@@ -1,6 +1,6 @@
 # Optimized Prompts
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/optimized-prompts~2xvk6" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/optimized-prompts~2xvk6" />
 
 👨‍💼 Our users are complaining that when they use the `suggest_tags` prompt, it's
 taking a while to run because it has to run a few tools to get the data it
diff --git a/exercises/05.prompts/02.solution.optimized-prompt/README.mdx b/exercises/05.prompts/02.solution.optimized-prompt/README.mdx
@@ -1,6 +1,6 @@
 # Optimized Prompts
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/optimized-prompts~2xvk6/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/optimized-prompts~2xvk6/solution" />
 
 👨‍💼 Great work! Now we're all set. User's can now easily get their LLM to suggest
 tags for their journal entries and it's optimized to run quickly and without
diff --git a/exercises/05.prompts/03.problem.completion/README.mdx b/exercises/05.prompts/03.problem.completion/README.mdx
@@ -1,6 +1,6 @@
 # Prompt Completion
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/prompt-completion~qflr7" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/prompt-completion~qflr7" />
 
 👨‍💼 As the user searches through the dynamic values it can input for the prompt,
 it would be nice to have auto-completion of values.
diff --git a/exercises/05.prompts/03.solution.completion/README.mdx b/exercises/05.prompts/03.solution.completion/README.mdx
@@ -1,5 +1,5 @@
 # Prompt Completion
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/prompt-completion~qflr7/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/prompt-completion~qflr7/solution" />
 
 👨‍💼 Great work! Now the user can get auto-completion of values for the prompt.
diff --git a/exercises/05.prompts/FINISHED.mdx b/exercises/05.prompts/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Prompts
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/break~3zgsz" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/break~3zgsz" />
 
 Great work. I'll bet you can think of a few more prompts to add to MCP
 servers you're thinking about huh?!
diff --git a/exercises/05.prompts/README.mdx b/exercises/05.prompts/README.mdx
@@ -1,6 +1,6 @@
 # Prompts
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro~cndmc" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/intro~cndmc" />
 
 Sometimes there are common workflows for people using your MCP server you want
 to make easier for users. You may not want your users to have to write the same
diff --git a/exercises/FINISHED.mdx b/exercises/FINISHED.mdx
@@ -1,6 +1,6 @@
 # MCP Fundamentals 🧱
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/outro-you-ve-finished-the-fundamentals~bj1ni" />
+<EpicVideo url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/outro-you-ve-finished-the-fundamentals~bj1ni" />
 
 Hooray! You're all done! 👏👏
 
diff --git a/exercises/README.mdx b/exercises/README.mdx
@@ -2,7 +2,7 @@
 
 <EpicVideo
 	title="Intro to MCP Fundamentals"
-	url="https://www.epicai.pro/workshops/day-1-setup-intro-and-tools/intro-i51jf"
+	url="https://www.epicai.pro/workshops/day-1-2-mcp-fundamentals/intro-i51jf"
 />
 
 👨‍💼 Hello, my name is Peter the Product Manager. I'm here to help you get
diff --git a/package.json b/package.json
@@ -17,7 +17,7 @@
       "hideNavigation": "1"
     },
     "product": {
-      "slug": "day-1-setup-intro-and-tools",
+      "slug": "day-1-2-mcp-fundamentals",
       "host": "www.epicai.pro",
       "displayName": "EpicAI.pro",
       "displayNameShort": "Epic AI",
