update slug

kentcdodds · kentcdodds · commit 500c79baaad3 · 2025-12-05T16:36:49.000-07:00
diff --git a/exercises/01.discovery/01.problem.cors/README.mdx b/exercises/01.discovery/01.problem.cors/README.mdx
@@ -1,6 +1,6 @@
 # CORS
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/cors-fibqe" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/cors-fibqe" />
 
 👨‍💼 In our MCP server's case, users will always be accessing us from either a different domain or a desktop application. This means every single request is cross-origin by nature, making CORS headers absolutely essential for our server to function at all.
 
diff --git a/exercises/01.discovery/01.solution.cors/README.mdx b/exercises/01.discovery/01.solution.cors/README.mdx
@@ -1,6 +1,6 @@
 # CORS
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/cors-fibqe/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/cors-fibqe/solution" />
 
 👨‍💼 Excellent work! Now our users can connect to our server from any domain without encountering frustrating CORS policy errors.
 
diff --git a/exercises/01.discovery/02.problem.as/README.mdx b/exercises/01.discovery/02.problem.as/README.mdx
@@ -1,6 +1,6 @@
 # Auth Server Metadata
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/auth-server-metadata-g2r2y" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/auth-server-metadata-g2r2y" />
 
 👨‍💼 Now that clients can connect to our MCP server from any domain, they need to be able to discover how to authenticate with our system. When clients want to access protected resources or perform actions that require authentication, they need to know where to go and what methods are available.
 
diff --git a/exercises/01.discovery/02.solution.as/README.mdx b/exercises/01.discovery/02.solution.as/README.mdx
@@ -1,6 +1,6 @@
 # Auth Server Metadata
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/auth-server-metadata-g2r2y/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/auth-server-metadata-g2r2y/solution" />
 
 👨‍💼 Fantastic progress! Now, clients can seamlessly discover how to authenticate with our system by accessing the standardized `/.well-known/oauth-authorization-server` endpoint. This means any MCP-compliant client can automatically find out where to register, authorize, and obtain tokens—removing guesswork and enabling smooth, standards-based integration.
 
diff --git a/exercises/01.discovery/03.problem.pr/README.mdx b/exercises/01.discovery/03.problem.pr/README.mdx
@@ -1,6 +1,6 @@
 # Protected Resource
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/protected-resource-8kue7" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/protected-resource-8kue7" />
 
 👨‍💼 For our journaling app it's crucial that clients can discover how to interact with our resource server in a standards-compliant way. The Model Context Protocol (MCP) and OAuth require that we expose a public metadata endpoint so that any client can learn how to authenticate and what endpoints are available. This endpoint must be accessible to everyone, without requiring authentication, because it's the first step in the OAuth discovery process.
 
diff --git a/exercises/01.discovery/03.solution.pr/README.mdx b/exercises/01.discovery/03.solution.pr/README.mdx
@@ -1,6 +1,6 @@
 # Protected Resource
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/protected-resource-8kue7/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/protected-resource-8kue7/solution" />
 
 👨‍💼 Outstanding achievement! Now, any client can discover how to interact with our journaling resource server in a standards-compliant way. By exposing the public `/.well-known/oauth-protected-resource/mcp` metadata endpoint, we've made it possible for clients to programmatically learn how to authenticate and which authorization servers to use—without any guesswork or manual configuration.
 
diff --git a/exercises/01.discovery/FINISHED.mdx b/exercises/01.discovery/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Metadata Discovery
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/outro-to-metadata-discovery-vmqxq" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/outro-to-metadata-discovery-vmqxq" />
 
 Congratulations! You've completed the first step in making your MCP server discoverable and accessible to any standards-compliant client.
 
diff --git a/exercises/01.discovery/README.mdx b/exercises/01.discovery/README.mdx
@@ -1,6 +1,6 @@
 # Metadata Discovery
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/intro-to-metadata-discovery-7idpi" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/intro-to-metadata-discovery-7idpi" />
 
 Modern applications need a way for clients to discover how to authenticate and interact with servers securely. In the Model Context Protocol (MCP), this is achieved through standardized metadata endpoints that describe both the resource server (your MCP server) and its associated authorization server.
 
diff --git a/exercises/02.init/01.problem.authenticate/README.mdx b/exercises/02.init/01.problem.authenticate/README.mdx
@@ -1,6 +1,6 @@
 # Authenticate Header
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/authenticate-header-0n13b" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/authenticate-header-0n13b" />
 
 👨‍💼 In EpicMe, the `Authorization` header is the gatekeeper for every journal entry. Its job is simple but critical: make sure that only requests with valid credentials can access or change journal data. If a request doesn't include this header, it shouldn't get through—no exceptions. Once the client has an auth token, it'll send that token in the `Authorization` header. If that header doesn't exist, then we know they don't have a token and shouldn't be able to access our server.
 
diff --git a/exercises/02.init/01.solution.authenticate/README.mdx b/exercises/02.init/01.solution.authenticate/README.mdx
@@ -1,5 +1,5 @@
 # Authenticate Header
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/authenticate-header-0n13b/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/authenticate-header-0n13b/solution" />
 
 👨‍💼 Fantastic progress! We've just ensured that every request to our journal app is properly challenged for credentials. Now, if a client tries to access protected resources without an Authorization header, the server responds with a `401 Unauthorized` and a clear `WWW-Authenticate` header. This makes it obvious to clients what they need to do next, improving both security and user experience (while keeping us complient with the OAuth and MCP Authorization spec). Only authenticated users can move forward, keeping journal data safe and access predictable for everyone.
diff --git a/exercises/02.init/02.problem.params/README.mdx b/exercises/02.init/02.problem.params/README.mdx
@@ -1,6 +1,6 @@
 # Auth Params
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/auth-params-vilat" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/auth-params-vilat" />
 
 👨‍💼 In EpicMe, when a user tries to access a protected journal entry, it's not enough to simply block them. We need to let them know what to do about it. If a request is missing the right credentials, the server should respond with a `WWW-Authenticate` header that includes extra details, called auth params, so the client understands what went wrong and how to fix it.
 
diff --git a/exercises/02.init/02.solution.params/README.mdx b/exercises/02.init/02.solution.params/README.mdx
@@ -1,5 +1,5 @@
 # Auth Params
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/auth-params-vilat/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/auth-params-vilat/solution" />
 
 👨‍💼 Great job! We've just made our API much more helpful for clients by including detailed auth params in the `WWW-Authenticate` header when access is denied. Now, when a request is missing the right credentials, the response not only blocks access but also provides a `realm` and a `resource_metadata` URL. This gives clients clear guidance on what resource they're trying to access and where to find more information, making it easier for them to recover and try again. This improvement leads to a smoother integration experience and helps clients build smarter, more user-friendly apps.
diff --git a/exercises/02.init/FINISHED.mdx b/exercises/02.init/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Initialize OAuth Flow
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/outro-to-initialize-o-auth-flow-5lxa5" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/outro-to-initialize-o-auth-flow-5lxa5" />
 
 Woo! You did it! You've secured our MCP server by requiring the `Authorization` header and returning a `WWW-Authenticate` header with helpful details. This blocks unauthorized access and guides clients on how to authenticate.
diff --git a/exercises/02.init/README.mdx b/exercises/02.init/README.mdx
@@ -1,6 +1,6 @@
 # Initialize OAuth Flow
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/intro-to-authenticate-header-xosav" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/intro-to-authenticate-header-xosav" />
 
 Modern web applications need a way to securely identify users and protect resources. The first step in this process is checking for an `Authorization` header on incoming requests. This is foundational for any OAuth flow.
 
diff --git a/exercises/03.auth-info/01.problem.introspect/README.mdx b/exercises/03.auth-info/01.problem.introspect/README.mdx
@@ -1,6 +1,6 @@
 # Introspect
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/introspect-pjgp6" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/introspect-pjgp6" />
 
 👨‍💼 Ok, so we've got the user's auth token, but what do we do with it? Our server needs to know:
 
diff --git a/exercises/03.auth-info/01.solution.introspect/README.mdx b/exercises/03.auth-info/01.solution.introspect/README.mdx
@@ -1,5 +1,5 @@
 # Introspect
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/introspect-pjgp6/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/introspect-pjgp6/solution" />
 
 👨‍💼 Super! You've successfully implemented token introspection, which transforms anonymous tokens into rich user context. Now our MCP server can identify who each user is and understand their permissions, enabling personalized experiences and proper access control.
diff --git a/exercises/03.auth-info/02.problem.error/README.mdx b/exercises/03.auth-info/02.problem.error/README.mdx
@@ -1,6 +1,6 @@
 # Invalid Token Error
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/invalid-token-error-lm5cu" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/invalid-token-error-lm5cu" />
 
 👨‍💼 When clients provide an authentication token that turns out to be invalid or expired, they need clear feedback about what went wrong. Without proper error messaging, users might think the service is broken or get confused about why their request failed.
 
diff --git a/exercises/03.auth-info/02.solution.error/README.mdx b/exercises/03.auth-info/02.solution.error/README.mdx
@@ -1,6 +1,6 @@
 # Invalid Token Error
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/invalid-token-error-lm5cu/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/invalid-token-error-lm5cu/solution" />
 
 👨‍💼 Excellent! We've enhanced our error handling to provide clear, actionable feedback when clients provide invalid tokens. Now users get specific guidance about token expiration instead of generic error messages, making the authentication experience much more user-friendly.
 
diff --git a/exercises/03.auth-info/03.problem.active/README.mdx b/exercises/03.auth-info/03.problem.active/README.mdx
@@ -1,6 +1,6 @@
 # Token Active
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/token-active-zbbw4" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/token-active-zbbw4" />
 
 👨‍💼 When we introspect an auth token, the introspection endpoint will return whether the token is currently active (because tokens can be revoked or expired) and we need to check for that in our resolution callback.
 
diff --git a/exercises/03.auth-info/03.solution.active/README.mdx b/exercises/03.auth-info/03.solution.active/README.mdx
@@ -1,5 +1,5 @@
 # Token Active
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/token-active-zbbw4/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/token-active-zbbw4/solution" />
 
 👨‍💼 Great job. Really checking the `active` property was just a simple change, but making it typesafe with discriminated unions was a nice bonus!
diff --git a/exercises/03.auth-info/FINISHED.mdx b/exercises/03.auth-info/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Auth Info
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/outro-to-auth-info-rh757" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/outro-to-auth-info-rh757" />
 
 Great work on this. You now know how to go from an auth token to user-specific information that will help you identify the user and their permissions in your server. Now on to getting that information into your MCP tools!
diff --git a/exercises/03.auth-info/README.mdx b/exercises/03.auth-info/README.mdx
@@ -1,6 +1,6 @@
 # Auth Info
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/intro-to-auth-info~3k9ug" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/intro-to-auth-info~3k9ug" />
 
 So the client sends your resource server a token. Sometimes this is enough, but often you need to be able to know who that token represents and the scopes associated to that token. This is often referred to as "introspection".
 
diff --git a/exercises/04.user/01.problem.token/README.mdx b/exercises/04.user/01.problem.token/README.mdx
@@ -1,6 +1,6 @@
 # Client Token
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/client-token-st24u" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/client-token-st24u" />
 
 👨‍💼 When we make requests using `this.db` (our db client), we need to include the user's authentication token so that the server knows who the user is and what they're allowed to access.
 
diff --git a/exercises/04.user/01.solution.token/README.mdx b/exercises/04.user/01.solution.token/README.mdx
@@ -1,5 +1,5 @@
 # Client Token
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/client-token-st24u/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/client-token-st24u/solution" />
 
 👨‍💼 Excellent work! We've successfully implemented user-specific database access by passing authentication tokens to our database client. This is a crucial step in securing our MCP server. It ensures each user only sees their own data.
diff --git a/exercises/04.user/02.problem.user/README.mdx b/exercises/04.user/02.problem.user/README.mdx
@@ -1,6 +1,6 @@
 # Require User
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/require-user-adoka" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/require-user-adoka" />
 
 👨‍💼 Now that we have the client authenticated with the token, let's make a utility to get the user and also provide tools and resources to retrieve the user data.
 
diff --git a/exercises/04.user/02.solution.user/README.mdx b/exercises/04.user/02.solution.user/README.mdx
@@ -1,5 +1,5 @@
 # Require User
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/require-user-adoka/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/require-user-adoka/solution" />
 
 👨‍💼 Excellent work! Now clients can retrieve information about the currently logged in user.
diff --git a/exercises/04.user/FINISHED.mdx b/exercises/04.user/FINISHED.mdx
@@ -1,6 +1,6 @@
 # Using the User
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/outro-to-using-the-user-zu3bw" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/outro-to-using-the-user-zu3bw" />
 
 Congratulations! You've successfully implemented user-specific functionality in your MCP server. You've moved from a generic MCP server into a personalized, secure system that knows who each user is and ensures they only access their own data.
 
diff --git a/exercises/04.user/README.mdx b/exercises/04.user/README.mdx
@@ -1,6 +1,6 @@
 # Using the User
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/intro-to-using-the-user-w1w8a" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/intro-to-using-the-user-w1w8a" />
 
 Now that we have the auth info, we need to get it into our MCP agent's context so we can make database calls with the user's token and also expose it to our tools and resources. With Cloudflare Workers, this is done through the `ctx.props` mechanism, which allows you to pass data from the request handler into your `McpAgent` instance.
 
diff --git a/exercises/05.scopes/01.problem.check-scopes/README.mdx b/exercises/05.scopes/01.problem.check-scopes/README.mdx
@@ -1,6 +1,6 @@
 # Check Scopes
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/check-scopes-xkjqu" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/check-scopes-xkjqu" />
 
 👨‍💼 We're going to start adding more fine-grained control to what our MCP server can do by adding scopes. Our authorization server already supports scopes, and it makes no sense for the MCP server to show tools, resources, or prompts that the user doesn't have permission to use anyway.
 
diff --git a/exercises/05.scopes/01.solution.check-scopes/README.mdx b/exercises/05.scopes/01.solution.check-scopes/README.mdx
@@ -1,6 +1,6 @@
 # Check Scopes
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/check-scopes-xkjqu/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/check-scopes-xkjqu/solution" />
 
 👨‍💼 Excellent work! We've successfully implemented scope validation utilities that give our EpicMe journaling app fine-grained control over what authenticated users can access. Now our MCP server can check if users have the required permissions before allowing them to perform sensitive operations like reading private entries or managing tags.
 
diff --git a/exercises/05.scopes/02.problem.validate-sufficient-scope/README.mdx b/exercises/05.scopes/02.problem.validate-sufficient-scope/README.mdx
@@ -1,6 +1,6 @@
 # Validate Sufficient Scope
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/validate-sufficient-scope-wwivw" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/validate-sufficient-scope-wwivw" />
 
 👨‍💼 Some users are authenticating with no scopes which results in having a valid token, but not enough permissions to actually do anything useful with the MCP server. It would be better if we could let them know up front that they don't have enough permissions and need a new token with the appropriate scopes.
 
diff --git a/exercises/05.scopes/02.solution.validate-sufficient-scope/README.mdx b/exercises/05.scopes/02.solution.validate-sufficient-scope/README.mdx
@@ -1,5 +1,5 @@
 # Validate Sufficient Scope
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/validate-sufficient-scope-wwivw/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/validate-sufficient-scope-wwivw/solution" />
 
 👨‍💼 Excellent work! Now users won't be able to access the MCP server if they don't have useful permissions.
diff --git a/exercises/05.scopes/03.problem.scope-hints/README.mdx b/exercises/05.scopes/03.problem.scope-hints/README.mdx
@@ -1,6 +1,6 @@
 # Scope Hints
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/scope-hints-p0c97" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/scope-hints-p0c97" />
 
 👨‍💼 When users try to access our EpicMe journaling app without proper permissions, they need clear guidance on what scopes are available and required. Without this information, clients can't know what to request during the OAuth authorization flow, leading to failed authentication attempts and frustrated users.
 
diff --git a/exercises/05.scopes/03.solution.scope-hints/README.mdx b/exercises/05.scopes/03.solution.scope-hints/README.mdx
@@ -1,6 +1,6 @@
 # Scope Hints
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/scope-hints-p0c97/solution" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/scope-hints-p0c97/solution" />
 
 👨‍💼 Excellent work! We've successfully implemented scope hints that guide clients through the OAuth authorization process. Now when users encounter permission issues, their client apps can automatically discover what scopes are available and request the right permissions.
 
diff --git a/exercises/05.scopes/FINISHED.mdx b/exercises/05.scopes/FINISHED.mdx
@@ -1,5 +1,5 @@
 # Scopes
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/outro-to-scopes-xywcb" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/outro-to-scopes-xywcb" />
 
 Congratulations! You've successfully implemented fine-grained access control for your MCP server using OAuth scopes. Your EpicMe journaling app now provides secure, permission-based access to different features and resources.
diff --git a/exercises/05.scopes/README.mdx b/exercises/05.scopes/README.mdx
@@ -1,6 +1,6 @@
 # Scopes
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/intro-to-scopes-kpt4u" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/intro-to-scopes-kpt4u" />
 
 When building secure MCP servers, you need fine-grained control over what authenticated users can access. OAuth scopes provide this control by allowing you to define specific permissions that clients must request and users must grant. Without proper scope validation, your MCP server might expose sensitive data or allow unauthorized operations.
 
diff --git a/exercises/FINISHED.mdx b/exercises/FINISHED.mdx
@@ -1,6 +1,6 @@
 # MCP Auth 🔐
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/outro-to-mcp-auth-b1y5y" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/outro-to-mcp-auth-b1y5y" />
 
 Hooray! You're all done! 👏👏
 
diff --git a/exercises/README.mdx b/exercises/README.mdx
@@ -1,6 +1,6 @@
 # MCP Auth 🔐
 
-<EpicVideo url="https://www.epicai.pro/workshops/day-7-8-mcp-auth/intro-to-mcp-auth~u45z1" />
+<EpicVideo url="https://www.epicai.pro/workshops/mcp-auth-ddk2h/intro-to-mcp-auth~u45z1" />
 
 👨‍💼 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
@@ -22,7 +22,7 @@
     "onboardingVideo": "https://www.epicai.pro/get-started-with-epic-ai-workshops",
     "product": {
       "host": "www.epicai.pro",
-      "slug": "day-7-8-mcp-auth",
+      "slug": "mcp-auth-ddk2h",
       "displayName": "EpicAI.pro",
       "displayNameShort": "Epic AI",
       "discordChannelId": "1446549245246177371",
