Primary Photo for Scott Spence

Bridging the Gap: Using MCP Tools to Stay Current with Svelte 5

Presentation byScott Spence

Asking an LLM about Svelte 5 doesn't get you much useful information, cut-offs in training data mean that when there's a rapidly changing framework the information can be irrelevant.

Just get the LLM to use the internet, init!? Yeah, I'm going to walk through a set of Model Context Protocol tools I use or have built, how I use them in Claude and Cline and (hopefully) do a one-shot prompt to build out a feature straight from the Svelte blog!

Similar Presentations
Cover Photo for Building Smarter AI Applications with MCP: Redefining Development for JavaScript Developers

Building Smarter AI Applications with MCP: Redefining Development for JavaScript Developers

Problem: Traditional AI application development often involves juggling multiple tools, APIs, and frameworks, leading to inefficiencies, complexity, and limited scalability. Developers are stuck in outdated paradigms that struggle to keep up with the growing demands of modern AI solutions.

Solution: The Model Context Protocol (MCP) offers a transformative approach to AI app development—essentially function calling on steroids. MCP represents a paradigm shift by streamlining the integration and management of core functionalities like file systems, databases, and other essential services through its innovative framework. By enabling seamless connections and robust functionality, MCP revolutionizes how developers build and deploy smarter AI-driven applications.

Description: This hands-on workshop empowers JavaScript developers to explore all facets of MCP development. Participants will learn to build MCP clients, set up MCP servers, and leverage existing MCP servers to create robust AI applications. Through practical exercises, you'll discover how MCP simplifies development, boosts efficiency, and delivers smarter AI-powered solutions. You'll also gain insight into how MCP's groundbreaking function-calling model enhances workflows, allowing seamless management of tasks such as file systems, databases, and more.

Key Takeaways: - Master the fundamentals of MCP and its innovative function-calling approach. - Build and configure MCP clients and servers from scratch. - Explore how to utilize existing MCP servers to streamline development tasks. - Gain hands-on experience in transforming traditional AI workflows into scalable, efficient models.

Chris Noring
Cover Photo for Precision vs. Prediction: The Trouble With LLMs and Libraries

Precision vs. Prediction: The Trouble With LLMs and Libraries

Abstract

Libraries and frameworks are where LLMs often break down: too much context, too many moving parts, and lots of hidden assumptions. In this talk, we’ll unpack why models struggle in this space and present our method for structuring library knowledge into digestible chunks. Using Svelte as the running example, you’ll see what goes wrong when models get it wrong, and how Tessl's approach can help them finally get it right.

Overview

Why frameworks and libraries trip up LLMs

Software engineering, among other things, requires precision in language, API patterns, and dependency versioning. But models are trained on snapshots of data that:

  • Are taken in the past, meaning they have no knowledge of a framework just released;
  • Contain mixed and sometimes contradictory information about the same package. For example, different versions without clear differentiation;
  • Provide an unbalanced distribution of information. Some packages are well-documented, while others have very little coverage.

We’ll unpack why this matters for developers relying on AI coding tools and introduce a practical tool to help.

Tessl's method

  • Structured, doc-like blueprints of a package’s API, best practices, and examples.
  • They give coding agents a reliable reference point while iterating, helping them stay aligned with how a library is really meant to be used.

Svelte as a running example

  • Svelte poses a particular challenge: LLMs often mix it up with other frameworks or fall back to using older Svelte versions patterns.
  • With our method, the same agent can navigate the framework more effectively, producing cleaner, more accurate code.
Maria Gorinova
Primary Photo for Scott Spence

Bridging the Gap: Using MCP Tools to Stay Current with Svelte 5

Presentation byScott Spence

Asking an LLM about Svelte 5 doesn't get you much useful information, cut-offs in training data mean that when there's a rapidly changing framework the information can be irrelevant.

Just get the LLM to use the internet, init!? Yeah, I'm going to walk through a set of Model Context Protocol tools I use or have built, how I use them in Claude and Cline and (hopefully) do a one-shot prompt to build out a feature straight from the Svelte blog!

Similar Presentations
Cover Photo for Building Smarter AI Applications with MCP: Redefining Development for JavaScript Developers

Building Smarter AI Applications with MCP: Redefining Development for JavaScript Developers

Problem: Traditional AI application development often involves juggling multiple tools, APIs, and frameworks, leading to inefficiencies, complexity, and limited scalability. Developers are stuck in outdated paradigms that struggle to keep up with the growing demands of modern AI solutions.

Solution: The Model Context Protocol (MCP) offers a transformative approach to AI app development—essentially function calling on steroids. MCP represents a paradigm shift by streamlining the integration and management of core functionalities like file systems, databases, and other essential services through its innovative framework. By enabling seamless connections and robust functionality, MCP revolutionizes how developers build and deploy smarter AI-driven applications.

Description: This hands-on workshop empowers JavaScript developers to explore all facets of MCP development. Participants will learn to build MCP clients, set up MCP servers, and leverage existing MCP servers to create robust AI applications. Through practical exercises, you'll discover how MCP simplifies development, boosts efficiency, and delivers smarter AI-powered solutions. You'll also gain insight into how MCP's groundbreaking function-calling model enhances workflows, allowing seamless management of tasks such as file systems, databases, and more.

Key Takeaways: - Master the fundamentals of MCP and its innovative function-calling approach. - Build and configure MCP clients and servers from scratch. - Explore how to utilize existing MCP servers to streamline development tasks. - Gain hands-on experience in transforming traditional AI workflows into scalable, efficient models.

Chris Noring
Cover Photo for Precision vs. Prediction: The Trouble With LLMs and Libraries

Precision vs. Prediction: The Trouble With LLMs and Libraries

Abstract

Libraries and frameworks are where LLMs often break down: too much context, too many moving parts, and lots of hidden assumptions. In this talk, we’ll unpack why models struggle in this space and present our method for structuring library knowledge into digestible chunks. Using Svelte as the running example, you’ll see what goes wrong when models get it wrong, and how Tessl's approach can help them finally get it right.

Overview

Why frameworks and libraries trip up LLMs

Software engineering, among other things, requires precision in language, API patterns, and dependency versioning. But models are trained on snapshots of data that:

  • Are taken in the past, meaning they have no knowledge of a framework just released;
  • Contain mixed and sometimes contradictory information about the same package. For example, different versions without clear differentiation;
  • Provide an unbalanced distribution of information. Some packages are well-documented, while others have very little coverage.

We’ll unpack why this matters for developers relying on AI coding tools and introduce a practical tool to help.

Tessl's method

  • Structured, doc-like blueprints of a package’s API, best practices, and examples.
  • They give coding agents a reliable reference point while iterating, helping them stay aligned with how a library is really meant to be used.

Svelte as a running example

  • Svelte poses a particular challenge: LLMs often mix it up with other frameworks or fall back to using older Svelte versions patterns.
  • With our method, the same agent can navigate the framework more effectively, producing cleaner, more accurate code.
Maria Gorinova

Get in touch!

hi@guild.host