Everyone Is Talking About MCP

Welcome to Syntax. In today's episode, we're talking about MCP.

In fact, a lot of people yeah. MCP.

You know MCP, you know me, all that stuff. A lot of people on Twitter have been talking about MCP. A lot of people on YouTube have been talking about MCP.

This is a thing that is seemingly, I would say, having a moment, right Node, so I figured we would, we would talk about it. Now what it is an AI topic. So those of you who are AI adverse, I think you should still know what this thing is. You should still take the time to understand it. But it is going to be a topic of AI. I know that is upsetting for some people.

Wes has created an ICP T shirt that says MCP, which is very funny.

Oh, that is great. I don't know how much longer I'll laugh at the AI generated T shirt designs, but that is a funny ICP.

Yeah. Yeah. Maybe for I don't know. Maybe the Europeans don't know. Can you give us the lure of what m ICP is? Well, hilling from Detroit, Michigan, my

my my stomping grounds. Yes. The Insane Clown Posse or ICP.

Yeah. They're an an American hip hop duo. Yeah.

Basically, it's like I don't I don't really know how to describe the music other than just kind of Node great. It it's rap music in a way, but it's rap music. It's like a very specific type of rap music. Man, I I I don't know the best way to describe it other than just being kind of like It's it's like a lifestyle. Like, the people that

people that listen to ICP ICP are are juggalos. Right? Just go search for the juggalo documentary.

Yeah. It's a cool world.

It's a cool world. Not. Hold on. I actually have an ICP story, Wes, related to web development. Lay it on me. Yeah. I I so I worked for an agency in Michigan for a long time, and it was a small agency.

And, oh, we used to bid on projects all the time. One of those projects that came up, ICP's website.

And we pitched them on it, and we won the project.

We won ICP's website. But then the owner of the company was like, guys, I've been doing some thinking, and I decided to listen to a lot of the ICP records, and I think we're gonna have to turn down this project.

And they let me tell you, they were a cool company too. I I like Yeah. It was all cool people that worked there. People were like but he was just like, I really just don't know if we want our company's name on this website. Like, I I really just don't know if that's what we want, and so we didn't get to do it. I I might have been the developer on that site. I might have had that on my resume.

So You would've sad. Man, that's funny. That's like the the poor guys that did the Kanye website. They're all so proud of that, and then they just had to come out and say Scott it from their records.

Oh, that's funny. Gotten, free tickets to the, whatever carnival thing they do. Yeah. I don't I don't think you would wanna go to one of those. And if you want to see all of the errors in your application, you'll want to check out Sentry at century.i0/syntax.

You don't want a production application out there that, well, you have no visibility into in case something is blowing up, and you might not even know it. So head on over to century.i0/syntax.

Again, we've been using this tool for a long time, and it totally rules. Alright.

So, MCP, what is this thing now that we're done joking about the Insane Clown Posse? Basically, it is a protocol. You think Wes, you think GraphQL, these are protocols for communication. Right? So this is a standardized protocol for LLMs to communicate with tools.

So whether that is your database, whether that is, you know, even, like, certain APIs, whether that's tools like Sanity at Sentry.io.

Nice. This is a protocol for, AI to be able to communicate with these tools in a, like, a more predictable but also a more connected way so that you can do things on behalf of yourself with LLMs or even just in general AI clients, whether that be Mhmm. You know, claw desktop or Cursor or Windsurf or any things like that. You can do things in a more connected way via this protocol Yeah. Which was created by the folks in the anthropic and anthropic in, like, November of twenty twenty four. So this is basically a protocol that's made this to be more standardized for these tools to talk to each other.

And we'll talk throughout the course of this episode about a little bit about some of these terms, but also what you can actually do with this stuff. Why is it useful? Why are people talking about it? But in general, just think about it JS MCP is the protocol for the connection between an API and the LLM.

Yes. If if you think about, like, the steps of of AI that we've had, like, we had at first, we had auto complete. Right? Oh, it knew that I wanted to type this thing, and auto completed it. And then and then we were able to, like, ask questions about chunks of Node. And and then we got agents, which could do things like like run terminal commands. They could Node. They can check outputs and inputs. It can, and it kind of recursively calls itself until it's it's finished.

And then that got us pretty far, but there's we always hit a point where the AI agent is not able to to do all of the things that that we want to do.

It's not able to to query a database. It's not able to book a flight for us. It's not able to, log in to your GitHub and leave a comment for yourself because it doesn't have access to those things, and it it doesn't know how to do those things. Mhmm. So the MCP, the main point of MCP is to provide a whole bunch of tools, which you basically code a whole bunch of tools, like leave a GitHub comment, merge pull Wes, close pull request, like a tweet, invite Scott, attach the you know, it could could literally be anything. And then you you code up all of these different tools, and then you provide them to the LLM and say, hey.

These are things you can Node.

And if you want to do them, here's what they look like. You know? Here it's essentially just giving it a library of functions that it can possibly run for you. Yes.

And what that means in regards to running functions and things for you is that if if you if you're a developer out here, you might be like, oh, it's just running stuff on my behalf.

Yes. In that regard, you kinda have to be aware of what these things have access to, what they could possibly do, and you might be able to get yourself in some sticky situations this way. So it is important to be careful with some of these tools. So some of the the terms that you have here would be like, an MCP host.

This is a program like Claw Desktop.

This could be Windsurf. This could be Cursor. It's in Versus Code as of yesterday.

It is. Yes. It is in Versus Code now.

You also have MCP clients, which is a protocol clients that maintain a one to one connection with an MCP server.

Okay? The server is basically a it's a server like you know a server, but it's a lightweight program that exposes specific capabilities through this protocol. Basically, we write servers to do API to to host your API or whatever. Wes is a very similar to that. It's a server that, again, just establishes

what are these functions that the AI can access and do. Yeah. And then the the client would be the way that you connect to it. So if you think about, like, an Yeah. A traditional API, your client might be fetch or or tan stack router or a WebSocket connection. But in in the case of, like, the people who are building, like, Versus Node, cursor, all these IDEs, they would be implementing the client library.

Yes. If you would only be doing that if you are building your own agent. Correct. So what are some thing like, why? Why do people care about this? Why is this interesting? What what does it matter? Well, let's give you some examples of some stuff you can actually do with this just broadly, before we talk about, like, what it takes to actually make one or or use them or anything like that. So, GitHub released their official MCP, Vercel. And you could imagine that this might be useful in terms of being able to communicate with an LLM or communicate with any sort of ESLint here to do things like open a PR, look at issues, maybe even analyze issues or things like that. Give me Yeah. Give me the the first twenty issues in this repository and tell me what they have in common. I don't know. You know? But, basically, it can do things like that. It can do anything that you would want like a GitHub API to do. In in typical API fashion, you're calling, like, a function to do things like potentially merge a PR or or open a PR or any of that kind of stuff. Now you could integrate that and do it via an LLM rather than via code.

I don't even yeah. I don't even think of it as, like, things that you would typically use an API for. It's things that you would typically use you for.

So for example, I hooked up the GitHub, MCP server, and I said, hey.

How many how many issues are currently open on the or how many pull requests are open on West Boss? And it it went open. It went in and said, oh, you have 28 pull requests open. Most of them are minor grammar and, spelling mistakes. So I was able to say, alright. Go through them and merge any that are clearly spelling or grammar mistakes. Take the entire blog post into context. Leave a nice reply. And they went through, and it emerged a couple for me. It left a nice little comment. Little nervous doing that, but Yes. Yeah. It worked really well in that, like, I you're able to use the, like, flexibleness of flexibility of an LLM.

We're like like, look at the pull request. Is it just like a simple spelling mistake or or grammar? Then, yeah, go ahead and merge the thing and leave a little comment. And it went through, and it basically, what it does is it it runs all of the different tools. So the here. Let me let me share my screen real quick. So here, I'm anyone who's not listening, I'm just looking at a list of all of the tools that are available. So the the GitHub MCP server, what it does, it fires up a little Docker container locally, and then it has, what, twenty, thirty different things. Create a pull request, update, create a branch, add issue comment, get issue, etcetera, etcetera. So, basically, we'll look at all of these tools and their TypeScript and say, alright. I think I will use this one to get a list of all the issues, and then I'm going to loop through each of those and and read them read through them, and then I will decide if if I would like to close it or merge it, then I will I will use the merge tool, etcetera, etcetera.

It works really well. I I was surprised at how nice and smooth it was to be able to do that. And and I previously would not have used AI to do that, or I would just, like, copy paste everything in into, like, an LLM and say which of these are which of these are worth merging.

Can you tell me how you got to this again, that little menu?

This is Versus Node.

It's Versus Code. With their

MCP. I was just just trying it out because it it VSCode launched agent mode and MCP servers and their next edit suggestion, and those are, like, the three huge things that people have been, like people left for Cursor four and and Windsurf four. So I was like, alright. Let's let's give it a shot.

And it's really nice. So I have this little mcp.json, and I have a list of all of the different MCP servers I want. And then it tells you how many tools are available in each of those servers.

Yeah. That's the thing that I've had a hard time with is making sure that the the chat, whether it'd be cloud desktop or anything, actually uses the MCP call. Like, I don't know if you've had any trouble with that. But, like, Claude, I had, for the YouTube MCP, I had it all set up correctly, and Yeah. Claude desktop was, like, doing everything in its power to not use it. And I was just had to be like, you have the you have the following capabilities.

Like, use these capabilities, which is crazy Wes Cursor had a much easier time with it Wes I'd say, specifically on YouTube, hey. Give me the the five most recent videos from our YouTube and output their their stats or something like that. And Claude would be like, I don't know what your YouTube channel is. And then, like, cursor would be like, yeah. Here you go. Because it had my API key. It knew what channel I had, via the configuration of it. So it's just like getting it to actually utilize the tools I found to sometimes be a giant pain. But I haven't tried the Versus Code with the notation.

In Versus Code, you can do a pound, and then you can actually explicitly name them. Ideally, you would just use English to say what you want. It would figure them out. But if you have too many tools, then it might pick the wrong one. So you can also explicitly tell it which one you want. So here, I just went ahead and said, how many issues are on the syntax f m forward slash website? You have Deno.

Summarize what they are about, and it's going off and running that. We'll see. Let let's talk about one that I actually built, and we'll come back to that because it it is a little bit slow, which is not an issue when it's doing work for you in the background. But when you're kinda just sitting there waiting for it to do things, it can be a little bit sluggish.

Yeah. So you wouldn't wanna do it for things that are easily accomplishable by you in one second. Right? You know? Exactly. Yeah. It's not exactly a savings at that point.

So I, I actually built one because one of the problems that I have with, AI is that it can't ever get logos for you, you Node, and I often wanna be, like, show the Chrome and and whatever logo. So I wrote a MCP server for SVGL, which is you told me about this. It's like a it's a website. It's a Raycast extension for getting logos for coding things. Right? So I wrote a little MCP server that just hit their API, fetched it, and then returned the SVG code. Oh. That's a perfect example of, like, go to this service, download this thing, and bring it back into my

my project. Yeah. No. That's a great idea. It's a demo for that. Playwright is another really good example for one.

You can kinda describe it as it gives your AI agent hands. So if I can go into my history here we go. Can you visit Syntax FM and tell me if there are any console errors? So that's kinda interesting. Right? Visit this actual website and open the console and see if there are any errors. And if this was the Syntax repo, it could maybe even find the actual issues that that were happening. Right? And then it so what it did is it fired up a headless or headful Playwright browser for me.

And and then it visited the website, and it says there are no issues. And then I said, are there an accessibility issues? So then it ran another tool called browser snapshot, which gives you sort of a accessibility tree of all the HTML.

See, that's the Syntax FM homepage.

And then it ran through that, and it found a couple issues that we could possibly fix. So that was good.

This is by the way, this is why I get so many garbage emails these days. Yeah. Because people are using these tools to just, like, hello, mister West Bos. I found these following issues on your website, and they're just churning them out. So, like, these, I don't Node, as much as I love this stuff, I also it just has created such a problem with

with people emailing me. We got one the other day. It was like, I love this episode, and the episode had not been released yet. I was just like, okay. You're just like, you found it in our our GitHub or something. I don't know what it was. Really? Oh. Yeah. I think I saw was that on Twitter?

No. It was on email. I got an email. Oh, really? Yeah. Oh, that's interesting. Yeah. They they probably scraped the the markdown files. But then I asked it, go ahead and give me the last 20 episodes, and it knew to click on the show's page. And then it knew to click on the show's page two to get another 10. And then it went ahead and and summarized all of them for us, which is is is amazing. So Yeah. It's almost like another scraping agent as well. Like, you know, visit these websites. And I've heard from a lot of people that their bandwidth is going way up lately, and it's because not because people are visiting their website, but these hungry LLMs are scraping the top 50 websites when somebody asks a question, compiling that all in and and pushing it out the other end. Yeah. Yeah. Interesting stuff.

Another thing that people are doing with the Century actually made one themselves, and, Kramer was telling me a little bit about this. David Kramer was saying, like, you know, the idea would be, like, from within a file to reference and be able to discuss, like, specific errors or look up, are there any Sanity, you know, errors that are associated with this file, etcetera.

Being able to, like, actually communicate with your error hunting platform directly from your code Bos as, like, a a cool use case for this. He actually just published a video too today that was talking about how they built the or how he built the MCP server. So, probably worth your time to watch it. I think it's pretty useful. Yeah. That's it's such a good use case of, like, what would you normally do as a developer? Well, you flip over to your Sanity, take a look, and you flip back to your your your code Bos, and

you try to line those things up. But wouldn't it be nice to just say, hey.

Is there fix all the issues? Like Yeah. It's funny that we've we've literally joked about this in the past Wes, like, the only Century thing Century doesn't do is is fix the code for you. And, like, that kinda does that now.

It's getting there. Yeah. That's for sure. I know, which is crazy. Yeah. Yeah. Which, again, if you're having, like, production software and people are using it, you kinda want it to be fixed really fast. So, if you could do that directly from your code Bos or even, like, supervise something as it is fixing the issues and things like that, it could be helpful. I did get the YouTube MCP server a rip, and I found it to be pretty bad, which is another thing that is, like, you are kind of at the the whim of the specific server. So I think some of them function and operate better than others. Like Yeah. The YouTube one specifically says that it's implemented the following API calls. Now I've used the YouTube API pretty extensively, so I know what these API calls can do.

And so, even prompting it and then having the MCP server say that it's going off and doing the thing and then actually returning wrong or bad information, very possible. Still very possible with these things. So that's not like they're always going to be a silver bullet, especially if you're at the whim of who wrote the server. Totally. But you could do things like compare my most four popular videos. Now I found it to be like, I would say, give me the the five most recent syntax videos, and it has our API key. Key. It has access to our channel. It has access to that API functionality, and it would still give us, like, five random videos from our channel. Oh. Because, like, that's not what I'm looking for. You know? I I don't know why. I haven't dove into it yet. But, again, these things are at the end of the day, they're still LLMs and Yeah. It is using this method, but it's not not a perfect science.

And and whatever MCP server for YouTube must have that ability to sort or whatever built in. Right. Yes. And it certainly is very early days for a lot of the stuff. A lot of the stuff feels janky or Yes. Like we'll talk about the the transport protocols in just a sec.

So it certainly feels very early, and you should definitely be very careful because I've seen lots of malicious MCPs. You know? You are letting a random website run random commands on your you can obviously have to prove them before they run, but you don't know Yeah. What they're actually doing. And those have been a lot of people who have been been hacked or had their, I don't know, cryptos

stolen and all that. They stole my ape. Yeah. Certainly Get your ape stolen. Don't go willy nilly

looking just trying every single MCP server out there as it can be a little bit little bit freaky.

We should say, though, that these are not just for coding. Like, Scott gave Scott good example of of YouTube, but there's there's other ones like, what, DaVinci has one? Yeah. That's so that's what I I found to be really cool. We'll share,

there's a, Smithery is a website that you can go to, like, look up some of these.

And there's also some repos like awesome MCP servers and stuff. But, yeah, I found the DaVinci MCP server. DaVinci Resolve is the video editing software that I really like to use. And you can do things like create timelines, add clips to timelines, or whatever, but you could imagine that could be handy to say, like, I I I don't know. I'm not I'm not even aware if this, MCP server could do this, but you could say, hey. Give me five random clips from my media pool. Cut them at random intervals. Throw them on a time ESLint. And this like, do those types of things that you could probably do with scripting in DaVinci, but, like, then you're getting into Lua and you're writing Lua scripts, which I've been doing, and it's not just it's not a lot of fun.

So, yeah, you can control applications like DaVinci with it. Even just, like, how do I do this is is often the question. Like, I I'll jump into Photoshop or Illustrator, and there's all these, like, three d video editing. There's all these, like, fringe programs where, like, I'm I'm okay at them, but, like, I'm not an expert at them. And often, I will just type into an AI. It's like, how do I add a motion blur in Photoshop? And it'll tell you, like, click on this, click on this, click on this, and here's all the the different options. And wouldn't it be Node step further? Is it just doing that for you or at least opening the context for where you're at or or sometimes you're, like, just trying to click on something, but you're not in the right Node. And the LM would know to switch you to the correct mode before you do that.

Yeah. Word. There's absolutely lots of them out there. Postgres is another really interesting one for coding because if you're building an application, the LLM doesn't know anything about the actual data in your database.

Mhmm. It might know about the schema. You know? It might need about but your config and your types.

But with the Postgres one, you can simply just say, like, show me the 10 most recent shows in our database or, what tables are in here, or even, like, I would I would imagine you could do something like create a drizzle schema for this existing database. Totally. Yes. Right? Like, drop all tables. It.

Drop drop all tables. Exactly.

But, like, you think about the kind of cool tools that you could build with, like, internal tooling.

You know? Give me the last, hundred sticker orders and show me the average amount spent per country.

Yeah. And just And that's what I was really hoping for out of the YouTube MCP server, which why I was so disappointed by it because I wanted to be able to analyze stuff better. And right now, I'm building my own set of YouTube tools that are doing exactly that, but it's doing it in code. And that's fine. That's totally fine. But, like, if I want a piece of specific analysis, like, you know, I have to write that code myself. And and and I actually have to have it in code. I have to Wes. I have to make sure it works, all that stuff, instead of just being like,

oh, give me the five most popular videos and tell me what they have in common. You know? Mhmm. So we'll talk about actually setting up a server or using the different servers. There's there's two, maybe three different kinds of transport protocols.

One of them being, standard IO, meaning that it's a script that the MCPs will call, and then that script fires up, and you can interact with it, and then it will it'll spin down then when you're finished. Right? The the Playwright one is like that. It'll spin up a Playwright instance.

You can interact with it, change pages, take screenshots, and then and then once you're done, it it will it will spin down and close that instance.

A long running MCP server is something that is always up up and running. Right? And that works on server sent events Wes you're simply just sending data back and forth the entire time.

Then they are now adding support for for streaming instead. Because, like, if you wanted to deploy a, MCP server to, like, a serverless function Mhmm. Vercel, pretty, pretty vocal in this area as Wes. It's not really possible. Right? You need a long running server.

Wouldn't it be nice just to have a serverless function that you can hit and then stream back and forth with it? And then once you're done, you can shut it down. So I think that that is probably going to be the more popular way to go about it. But right now, at least most of the tools for building a server, you either go with one or the other. And and usually the standard IO ones are they're often just Npm scripts.

Yep. Sometimes there are Docker containers that you'll run locally.

Depends on, of course, the the different tooling that is necessary.

Writing your own, there's a couple, like, tools out there. So the one I use is called FastMCP, and it's sort of like the jQuery of writing MCP server. Just a bunch of, like, handy little functions or maybe the Lodash

of it. And

that is written the the the that was written in Python, but somebody has, like, ported the exact API to TypeScript, which is really nice.

And then the, like, Claude themselves has the MCP TypeScript library, which is more of the lower level APIs. You could build one with that. Cloudflare is is starting to do a bunch of work in this space as well. I was at a conference last week where Angie Jones gave a talk. She works at this company called Block, and they're working on this thing called Goose, which Oh, yeah. Is another way to to sort of get up and running with that as well. So there's I think it it feels very early in all of this stuff. So if you're dipping into it, it's it'll probably feel a little bit rusty here and there, but I think everyone's trying to figure all this stuff out. It's only been, I think, November of last year is is when Flod announced it. So we're only, like, six months into this. So I I think that this will really change, but the standard has been adopted by all of the editors. It's been adopted by OpenAI.

It's obviously by Claude. So it's the standard is here.

And what that standard looks like in six months, a year from now will probably look a little different. Yeah. It'll probably have evolved a little bit. I do wanna say, you were mentioning that the FastMCP

one thing you'll notice with a lot of these, like, starters and tools is that data validation and general, like Yes. Data types are important. So most of them will be using Node or archetype or Vali Bos. I see most of them use Zod, to be honest. So Yes. Whether that is for the inputs or or outputs or whatever, you're giving the LLM that much more context by telling it what the data should look like. So very widely used a tool to do data validation.

This yeah. Because you you need to make sure that the data coming in is exactly of the type that it expects. Right? If you're asking an LLM to be very precise Yes. You need something like that. So FastMCP uses standard schema. Remember we did the episode explaining what standard schema JS, Wes, basically, somebody who needs to add validation to their library can use standard schema, and then people can use any standard schema compatible validation library. And this is, like, one of the first, like, new instances I've seen of something using it. So FastMCP will allow you to use Node or ValleyBot or, what's the other one?

Archetype.

Archetype.

Those are the, obviously, the big three, but anything that are standard schema compatible. That's syntax episode eight seventy three if you want to. You can get that listen. Yeah. Other parts of MCP. So we've pretty much been talking about tools, in MCP, but there are other parts of it. There are resources which has not been implemented by any of the editors yet. So in my example of the downloading the icons Mhmm. A resource would be something that is returned from that. And and you could say a resource would be an image. You could say a resource is, like like a video or a PDF or it Sanity anything. Right? Anything you can then feed back to the LLM for additional context.

And in my case, the resource would be returning an SVG image, and it didn't work. And that's because none of the editors support, MCP resources yet. So I had to go a different way where I I just returned the SVG Node, and then I had I had the AI just Scott it into into a file. You could also just use Node APIs f s dot write file, something like that.

So that's something that will probably be better supported in the next two, three, four months, I bet.

Yeah. Interesting. Yeah. There's also MCP prompts, which Yarn, like, reusable prompts, templates, workflows that people who are using your servers can use. Again, those are not supported by anybody.

And then there's also roots, which I found this out the hard way where I downloaded the Scott, and it literally put it on forward slash because it doesn't know where it's it doesn't know where it's running. So if you can get if you can provide it a route like the currently open folder, then, you'd be in a bit better shape.

Interesting. All of these are bit I'm I'm linking to the modelcontextprotocol.i0 docs for each of these as well if you want to dive into them. We'll have these links available to you in the show notes.

Mhmm. We should also say there's there's also, like, Python, Java, Kotlin, and c sharp SDKs for MCP. So you don't have to write it in JavaScript, although you probably should because it's the best.

Yeah. Yes. Right. We are not biased on that one. I'm also going to link the awesome MCP server, GitHub.

There's a lot. You know what? I find this personally to little be a little bit overwhelming. It's like, I hear about this new thing. I'm gonna go try it out. I go to the awesome MCP's repo, and there's, like, 10,000 things on this already. And it makes me feel like I'm late to this. Oh, crazy.

So there's a lot of people building on this right now, and who knows if all of these are fully featured or working correctly or whatever.

But if you wanna be inspired or even just see what you can possibly experiment with this, if this sounds interesting to you and you want to give some of these a rip, this awesome MCP's GitHub repo or

the, link that I had earlier on in the show, the smithery Yarn good places to at least hunt for some of these things to see get inspired maybe. Yes. Again, be very careful. Don't just install a bunch of random ones. But Yeah. They can mess you up. Some some fun stuff in here. You know? Like, I'm Yeah. I'm really excited about this because I have to like, one example is I have to go to, like, eight different bank accounts four times a year and download

all my transactions. I'm not giving this access to my bank accounts. I'm not doing that. Yeah. That's probably not a good idea.

But, like, Node. I'm thinking, like, could I build one with with Playwright Yes. That is flexible enough that it could click the buttons for me Yes. And and download everything. I don't know if I can or not. It's like a fifteen, twenty minutes of clicking.

Do I spend two days Yes. Building that? Yes. I think I should. That makes sense. Go for it.

Developer math. Alright. Yeah. I think that's it. Let us know your favorite MCP Vercel. That's kind of the big thing JS I'm I love hearing from everybody about what are what are they using it for because it's it still feels so early.

Yeah. Are you down with MCP? Let us know. We wanna Node, again, what you're using it for. If you think it's stupid, if you think it's great, if you think it's going to delete your entire database, whatever, we wanna hear all about it. What have you have you done anything cool with it? Just let us know.

Leave a comment. We we see your comments on Spotify. We leave your comments on on YouTube JS a great place to see that, all of the above. So let us Node, and, I don't have anything else about this. Wes, do you? That's it. Thanks, Eric, for tuning in. Catch you later. Peace.