945: Chrome Dev Tools MCP Server

Scott and Wes dive into Chrome’s new MCP server; a dev tools API powered by Puppeteer that gives your scripts, editors, and AI agents full access to Chrome. They break down how it works, what it can (and can’t) do, and how it might change debugging and automation for developers Show Notes 00:00 Welcome to Syntax! 01:15 Syntax San Francisco Meetup. 01:55 We need your Spooky Stories! 02:42 What is an MCP Server? 04:28 MCP servers are not only for code editors. 06:43 Brought to you by Sentry.io. 07:49 Dev Tools MCP is similar to Puppeteer. 09:20 Setting up an MCP Server. 11:36 Example of MCP with Dominos Pizza. 13:23 Accessing Dev tools from your editor. 14:23 In VS Code, you can “Open Link”. 15:22 Using the MCP server. 16:26 Chrome has Debug insights inside of chrome’s dev tools. 18:38 Real world things the Chrome MCP server can do. 18:43 Analyzing performance. 19:55 Taking screenshots. 21:17 Performance fix feedback loop. 22:33 Remote connecting browsers. 24:54 Browser-use. 25:18 What are the limitations? Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Wes Bos?

  Welcome to Syntax. Today, we have a show on Chrome's new DevTools MCP server. This is actually kind of nifty as a way to both help you debug as well as figure out what's going on your website programmatically controlled, figure out network issues that are going on. There's a whole bunch of use cases. So we're going to talk about that today. My name is Wes Boss. I'm a developer from Canada. With me as always is Mr. Scott Tolinski. How are you doing, Scott?

• 0:29Scott Tolinski?

  Oh, man, I'm doing much better. Last week, at the start of the Ricky episode when we recorded, within like the first couple of moments, and it might have been before we hit record, I chipped my dang tooth on the glass straw. So the entire episode, I'm just sitting there like trying to like have a conversation and my mouth is just like killing me. So

• 0:51Wes Bos?

  Was it like a big, big chip?

• 0:54Scott Tolinski?

  It's a, nah, you can kind of see it. It's this tooth right here. It just kind of chips in, kind of took out a little bit of the bottom. So no good. I haven't gotten anything done about it because it's gotten kind of less sensitive, but I'll get it looked at, I suppose.

• 1:09Wes Bos?

  Awesome. Well, a lot of awesome. Awesome. MCP server, though. Before we get started, two things. Meetup and spooky story submission. We need you for both. October 27, we are going to be doing a meetup in San Francisco at Bear Bottle Beer Garden in Salesforce Park. We're in town for GitHub Universe. You don't have to actually be going to GitHub Universe to go to this. It's open to anybody. We're going to have a bunch of drinks, a bunch of swag, really good time. So if you're anywhere in the California area, or somewhere in California, or anywhere you want to fly down, come on out. October 27, it's going to be a, go to syntax.fm/meetup and you can grab a ticket. They are free, but you do have to

• 1:53Wes Bos?

  reserve one because space is limited. Second,

• 1:57Wes Bos?

  Halloween's coming up. We need your spooky stories. This is an episode we do every single year where we read off the most terrifying spooky stories about web development in general. So have you taken down prod by accident? Have you published something that you shouldn't have? Have you let an SSL certificate expire? Have you dropped a database by accident? Deleted all the records? We want to hear your most stick-your-head-in-the-ground stories for Halloween. These are always awful to hear, but you learn a lot. So please go to syntax.fm/ spooky and submit your story. We keep absolutely everything anonymous. So tell us your words.

• 2:42Wes Bos?

  So let's talk about like what the hell these things are really quickly, just so you have context if you've never used these things before. So Chrome Dev Tools, you probably know what those are, right? Those are the dev tools where you can pop it open. You have your console. You have your network access. There are several tabs in there. Actually, like, maybe, we haven't done that episode in a while. It's like tips for the dev tools. I think there's some nuggets in there. Everybody uses console and that's about it. And there's, there's so much more in there. MCP server is a way to provide AI additional tools. So like, an AI model on its own, you can, you can talk back and forth to it, or you can give it content and it will give you content back.

• 3:23Wes Bos?

  But when you needed to do things that it can't do, like, like, visit a website, or like, I built a MCP server that fetched the latest currencies, you know, like, just, just different tools. Like, one tool I've made is, is the ability just to do math, right? Surprisingly, AI is not, not great at math. And when you use ChatGPT, they're using all of these tools behind the scenes. You might not necessarily know it, but it's not simply just this, the single model that, that knows everything. So.

• 3:56Wes Bos?

  MCP servers are super useful and being able to use them when debugging and build websites is extremely useful. And I'm really glad to see that Chrome has now rolled out a MCP server that will allow your AI tool to visit websites, click around, look in the console, look at your network, run tests, screenshot, grab the HTML, all of that good stuff for you. And it can be very helpful for a number of reasons. We'll talk about that. But MCP servers, not just for your code editor, right Scott?

• 4:32Scott Tolinski?

  Yeah, there's a lot of tools there. And I think when at first I was like, okay, it's the dev tools, MCP, that gives us access to the dev tools. But it's more than that. It is fully automating the browser. And initially, when I thought about this, I did think about how many little workflows that I'm automating right now, we're doing with Playwright, or maybe even the agent itself is just like trying to fire up the dev server and visit the site, how much more of that you could get finely tuned in a way, but also develop really nice feedback loops of fixing issues potentially, or examining things that are actually rendered on the page, getting access to that massive set of tools, at least most of them that exist

• 5:15Scott Tolinski?

  in the Chrome Dev Tools. This got me very excited. And I think more and more lately, as I use a lot of these agentic flows, the more I do this, I find MCP servers to be, man, they are just, I'm really excited by MCP. And I was at Microsoft's campus, and Kenzie Dodds was there. And he's like so up on MCP. And he was just chatting about it the whole time. And it's gotten me into such a position where I'm like really feeling the future of MCP, and like seeing the big picture here about why these things matter. So the fact that

• 5:57Scott Tolinski?

  soon after those conversations were taking place, the Chrome Dev Team releases this, and it's like, yes, okay, we have another really great MCP tool. That we can take advantage of. I see a lot of possibilities and then when you link these tools up like there's a Figma MCP server. You could essentially take a design. You could take it from Figma, you could bring it into code, you could load it up and you could verify it. You could take screenshots, you could compare the screenshots. There's so much potential where you, when you're combining these tools that I'm pretty stoked about.

• 6:31Wes Bos?

  That's the idea at least, right? Whether that is doable yet, I certainly think that we will be able to do that at some point, which is kind of exciting.

• 6:41Scott Tolinski?

  Yeah, no, very exciting. Yeah. But before we get too deep, Wes, let me do, take a moment to talk about Sentry before we. Yeah, I, a quick little ad break here. Sentry is amazing and Sentry has a great MCP server. But Sentry's AI tools, other than that are really great. I had a really awful bug in an app lately and I, I stuck Seer on it, which is their AI tool that kind of gets through the garbage and finds the root cause of issues. And man, this was like not, like I, I read the logs, I read the Sentry errors, I read everything and I could not find it. And I clicked the Seer button and was like, hey, did you look at this? ENV variable, make sure it's set. And I'm like, yeah, of course it's set. Seer thinks.

• 7:26Scott Tolinski?

  And I went and it was a typo and the ENV definition, it was just a typo.

• 7:31Wes Bos?

  Oh, man.

• 7:33Scott Tolinski?

  Seer found it and I, I don't know how it found it. It was magic to me. So.

• 7:38Wes Bos?

  Yeah.

• 7:39Scott Tolinski?

  Yeah, wild stuff. So thank you, Sentry. So check it out at sentry.io forward slash syntax. Sign up, get two months for free. These are serious tools and man, really loving them.

• 7:48Wes Bos?

  So the Chrome DevTools MCP server, it, it shares a lot of overlap with the like puppeteer. Yeah. MCP server, meaning that like it, what it does is when, when you, when it needs to visit a website, it will fire up an instance of Chrome. It actually fires up a, a new instance. It, it won't connect to your existing, like you just have your regular Chrome open up and everything. And, and there's a couple of reasons for that, like the, the technical reason behind it is that. You need to have remote debugging running on a Chrome instance in order for remote debugging to to be able to communicate back and forth with it. So that's the one technical reason and probably the other reason because immediately I was like, well, I can't

• 8:31Wes Bos?

  let's just connect to my I have my my regular thing. I have all my dev tools open. I have all my extensions, you know.

• 8:37Scott Tolinski?

  I got my stuff.

• 8:39Wes Bos?

  I got all my stuff here. Just connect to that one. Don't make another one. And I still hope that they will figure out some way to do that. And I know that I can fire up my own remote debugging, but the reason behind is is security, because like you you probably shouldn't give a rogue AI agent, which has other MCP tools hooked up to it as well, which could be also malicious. You know, there's nothing from stopping another MCP server

• 9:05Scott Tolinski?

  Yeah.

• 9:06Wes Bos?

  from trying to use this one, visiting your bank account and then sending all of your money to somebody else. So the certainly a security issue there. So that's why it fires up a brand new instance of Chrome that you have. So getting MCP server set up is you go into wherever you configure your MCP server. So whether that's your chat GPT or Claude chat, or whether that's your your VS code or your cursor, or whether that's you're simply writing a script with like the OpenAI SDK and you simply want to provide a list of MCP servers.

• 9:45Wes Bos?

  You just give it this NPX command and it will fire up an instance of that and how it gives you access to all of the tools. In VS code, it actually is kind of nice because it gives you a listing of what all the different tools are. So you can see

• 10:01Scott Tolinski?

  The VS code MCP stuff has gotten a level up.

• 10:05Wes Bos?

  Yeah, like list console messages hover handle dialogue get network request, right? I think the puppeteer one has a bit more of tools, but I've I've been actually able to use most of these things, which is like navigate to a page, find an input, enter in the thing, type some text, hit OK, wait for 10 seconds, look for a thing on the page. So you can you can programmatically control your website with most of these simply just by asking in the chat.

• 10:35Scott Tolinski?

  Yeah, I'm excited for that. And like you said earlier off the jump, like beyond coding, you could automate some real world stuff with these things, right? More than just, yeah, you connect.

• 10:49Wes Bos?

  Let's do an example here.

• 10:51Scott Tolinski?

  Yeah, my brain initially goes to, I can use this to debug, I can use this to performance track, I can use this to, you know, work on the web. But like, you can also connect your MCP server and you can say, you know,

• 11:07Scott Tolinski?

  let's go to scottzalinski.com and grab the first blog post there and use that blog post to create a demo. I mean, I guess that's coding too. You could have it automate things within the browser. Now, I'm currently using Comet to do some of that, right? And I think that world is still opening up for a lot of people, like absolutely automating using the browser with these tools. Yeah.

• 11:36Wes Bos?

  So here's an example. I just said, visit Domino's Pizza. I spelt it wrong and showed me the sizes of pizzas that they sell. So it fired up a new instance, took a snapshot of dominos.com, clicked on some pages, it's clicking around, it's navigating around, taking more snapshots. It's basically just looking for what it wants. It went to aboutdominospizza forward slash pizza sizes, like it just imagines. So obviously, it's not perfect. There we go. And ended up finding pizza size offered. It's medium and large, just maybe, maybe a good example of where it's not perfect, because obviously, they sell more of those. But that's just a perfect example of how you can use it to programmatically visit sites. And I think that-

• 12:19Scott Tolinski?

  But also Wes, also, you could have web search in any of these tools, do the web searching for you, retrieve that URL, the exact URL, and then pass that along to the Chrome Dev Tools MCP server to do that, instead of having like the AI try to just guess.

• 12:38Wes Bos?

  Yeah, exactly. Try to figure it out. I also asked it to visit my own personal website and tell me how many hot tips were there. And it first went to the first page. And then- It told me that there was 433 because it found it on the pagination. And then I said, find the 152th hot tip. And it just imagine the URL structure. So I had to tell it, hey, look at the, look at the anchor links, you know?

• 13:06Scott Tolinski?

  Hey.

• 13:06Wes Bos?

  Look at the, you just imagine what the pagination URL was, right? So it's just one tool out of many. I think you have to do a lot more prompting and writing, writing instructions for it to get it to work really well.

• 13:21Scott Tolinski?

  Yeah, yeah, just another tool.

• 13:23Wes Bos?

  One big thing I've, I've been interested in this is, is one of them was like being able to programmatically visit websites and do scraping and whatnot. But the other one was simply just getting access to the console errors and, and pushing that back into the chat. Because that's a big one for me where if I'm running the terminal within my editor, the terminal, like if you have a server running, those, those errors are pretty good. It's not perfect. I'm still, still frustrated at the like firing up a new server and getting the errors back from the terminal into your chat.

• 14:03Wes Bos?

  But I have not found a great way to, to do that with, with client side errors, right? So there's kind of a couple of ways you can go about this, right? If you want your console logs to show up and be accessible to your chat, especially when you have like syntax errors and, and, and things that are thrown, there's a couple of options, right? So in VS Code, you can say open link and then I have a VIT server running on port 5173. But getting this like debugs, you can see this is the actual browser debug console. Getting this information into the chat, like I've asked it, I, I must be missing something here, but like I, I don't think that the chat

• 14:46Wes Bos?

  has context into this debug console, right?

• 14:50Scott Tolinski?

  Did you check the tools? The, there's like a little tools dropdown or something.

• 14:54Wes Bos?

  Yeah, yeah, right here.

• 14:56Scott Tolinski?

  Yeah.

• 14:57Wes Bos?

  Edit, fetch, extensions, problems, right? Like it can, it can access the problems tab.

• 15:03Scott Tolinski?

  Interesting. Where's the debug console?

• 15:05Wes Bos?

  Yeah, but I don't see anything where it's like, has access to the debug console, which is frustrating. So like usually I just have to copy paste it into here. But like, wouldn't it be better for it to just know what errors were happening in my console? That would be really nice. So the MCP server will have the ability to do it, right? So if I stop this here and I'll say, "Visit localhost 5173 and see what the console errors are." So now it's running the MCP server and then it ran the tool list console messages. And then it found two errors. The Fab icon is missing.

• 15:49Wes Bos?

  And then it also found the unexpected token. So that was great. That was, that was totally connected where I said, "Visit this website and figure out what's going on in this case." Only thing it didn't do is fix it, which I guess I didn't ask it to do that. So I'll just say, "Go ahead and fix it." And then it should be able to apply that in my index HTML. There we go. Beautiful.

• 16:13Scott Tolinski?

  Yeah.

• 16:14Wes Bos?

  The other, sorry, one more.

• 16:15Scott Tolinski?

  Haters are gonna say that you could have fixed that yourself.

• 16:18Wes Bos?

  I, impossible. I needed to boil the ocean in order to find the missing semicolon. The last thing is that Chrome itself has like AI insights built right into DevTools. So if you have a console error and you turn on the AI insights in Chrome, it will actually suggest to you how to, how to fix it. Now, it's, it's kind of like a weird world because.

• 16:47Scott Tolinski?

  How do you turn those on? Sorry.

• 16:49Wes Bos?

  Yeah. Let me bring it in here. So this is my like regular Chrome here. There we go. So I brought back this, this actual error here. And unexpected token. And then there's a "Understand this error." You can click on it.

• 17:02Scott Tolinski?

  I don't have that.

• 17:03Wes Bos?

  I haven't been using. So it's somewhere in your settings.

• 17:06Scott Tolinski?

  Okay.

• 17:07Wes Bos?

  You can turn it on. Here we go. "Turn on console insights to receive AI assistance." Okay. Well, for some reason it turned itself off. So here we go. You go to Settings, AI Innovations. Turn that sucker on.

• 17:21Wes Bos?

  Okay.

• 17:21Scott Tolinski?

  Oh, I don't not have this in Comet browser.

• 17:25Wes Bos?

  So. Yes. So I was using.

• 17:27Scott Tolinski?

  Comet browser. No, thanks.

• 17:29Wes Bos?

  And I I've been using Edge for like over a year now, so I kind of missed it. And then here we go.

• 17:34Scott Tolinski?

  It that makes sense. It's not part of Chrome. It's part of Chrome.

• 17:37Wes Bos?

  Exactly. Yeah, it's the the browsers themselves. I think Firefox is also getting something similar to this as well, and I wouldn't be surprised. But my my question here is, is like, do we need to bring all of these? All of the dev tools to the editor?

• 17:52Scott Tolinski?

  Yeah.

• 17:53Wes Bos?

  Or or should the Chrome itself just be the the editor? Right? Like it it knows about all of my files. It knows about everything. It knows about all the requests. I actually asked the folks at Chrome, I had a call with them the other day. I was like, like, at what point are you just trying to bring everything out of Chrome via MCP servers into your your editor? And at what point would it make more sense to just make Chrome itself the editor? Right? Like, they tried that years ago with the like, local mapping and like. But it never it never cut on. I don't think it will ever cut on because you're you're essentially just rebuilding VS Code at that point.

• 18:30Scott Tolinski?

  Yeah.

• 18:31Wes Bos?

  But I thought that was kind of interesting.

• 18:34Scott Tolinski?

  Yeah, it is interesting. It is one of those things that comes up all the time.

• 18:38Wes Bos?

  Let's talk about what can the Chrome MCP server do other than visit things and get your console? Right? Analyze performance and make changes based on that. That's probably the biggest one is this site feels slow? Or what's my largest contentful pain? You know, all of those web dev metrics? You can ask it to look at those stats and and figure out what is actually causing it. So I asked the Chrome MCP server, can you visit syntax.fm and list all external fetch XHR requests that are made within the first 10 seconds? So it went ahead and found all that. And one kind of interesting thing, I didn't even know we were doing this, but it was hosting. We're hosting our fonts on your domain name, tolin.ski.

• 19:21Scott Tolinski?

  Yeah.

• 19:22Wes Bos?

  So.

• 19:22Scott Tolinski?

  Yes.

• 19:23Wes Bos?

  That's something I didn't know. And I also asked it like. What the biggest downloads were and it went ahead and figured that out. I said, is there any bundles on my personal website that were too large that could be possibly slowing the website down? And I feel like it did a pretty good job at that. Whereas like, obviously, I can just scan that really quickly and I know, but for people who don't necessarily know what is too large, you know, what are possible performance problems? It's nice to be able to just type it in the box and get that info.

• 19:54Scott Tolinski?

  Yeah, it's also nice to be able to take a screenshot from this because again, you could have a workflow where you have a design, you take a screenshot, you compare the design with the screenshot, whether that the design is potentially coming from like a Figma MCP and be able to verify, you know, what it's off, what's, what's not right? Because I do find that AI struggles with UI stuff pretty consistently. And so being able to have those tools are really nice. But also, you could even take a screenshot so that way you could know what the AI is even seeing when it's doing some of these tasks. Like, there's nothing worse than something failing and you're not exactly sure exactly what, what's going on.

• 20:33Wes Bos?

  The amount of times that I've said, it's just a white screen, or you just put black text on black tech on black background is, is huge, which it's another point that is like, the accessibility tools are not available in this MCP server. And I think that would really help. But yeah, the amount of times I've had to just simply screenshot something and put it into the chat and then it goes, ah, I see. So yeah, the screenshot tool is super helpful. Still, writing files with chats is seems to be a big problem. In this case, I had to put it in a temp directory and then asked me to run a move command to move the file from the temp directory to my, my local file system.

• 21:17Scott Tolinski?

  Mm hmm. Another really great opportunity here is to set up a feedback loop of performance fixes. There's a ton of stuff inside of Chrome Developer Tools from last, Contentful Paint, last Contentful Paint. Man, we did a whole episode on largest. Man, I'm so bad with words and acronyms. Largest contentful paint. There's a whole bunch of these tools and they're available to these MCP servers to be able to go off, find the issues and then potentially take that information back, pipe it back in and fix the problem. Which is just this nice loop that you can get of performance fix, performance fix, console log error fix, you know, a nice back and forth there.

• 22:02Wes Bos?

  There we go. I just ran it on syntax.fm and it came back with, look at all the raw data for the performance stats on syntax.fm and now it's going to go ahead and LCP 744. This is a good LCP score according to core web vitals. Good. LCP breakdown.

• 22:22Scott Tolinski?

  Yeah, this is actually another opportunity is give me plain English about these things, right? Like run perform and then actually just tell me, explain like I'm five. What is going on with the loading in the site?

• 22:33Wes Bos?

  So this is obviously Chrome only, but the question is, is like, not everybody is simply using this on a desktop. Right? If you are using it as part of a, a part of a script or you're running like Claude code on a server or something like that, then you need to be able to give it access to a Chrome instance if it is unable to spin one up itself. And you can, you can mostly run like puppeteer a headless on most, on most of these servers. I've done it many times. But if you have a Chrome instance that's simply just running, like you could have a Mac mini in your office. You could run it and expose the dev tools IP address to the internet.

• 23:17Wes Bos?

  And, and then you can give it that actual URL and then anytime that MCP server needs to use a browser, then it will simply just, it'll call out to that external Chrome instance.

• 23:29Scott Tolinski?

  You could use TailScale or anything like that. I, I run a Mac mini right there that I do a lot of remote stuff on, so.

• 23:34Wes Bos?

  Yeah. TailScale, CloudFlare Tunnels, all that good stuff. Might be a good option, although you have to worry about like, you're just opening up a browser to the internet. So you make sure you put some authentication or IP whitelist, something like that on there.

• 23:50Scott Tolinski?

  Yeah.

• 23:50Wes Bos?

  I do think that you can use this with Edge. So when you start up in Microsoft Edge, you're one of the flags you can run it is the remote port and it will give you a port and it'll start up a dev tools remote server that you can remotely connect to. So I believe with the flags that you pass to the MCP dot JSON, you can pass a, there's, they have this thing called connect URL in the docs that is simply just mentioned and there's no examples. It's not even part of the docs. It's just in like one of the little blurbs. So I'm pretty sure you can use that to connect to a browser that is not Chrome. So if you're running like a Chromium instance,

• 24:33Wes Bos?

  or I'm assuming an Edge, I don't know that you necessarily would want to because I don't see the benefit to it right now. If you were to use a different one, it's not like it's going to be using your logged in state of your Microsoft Edge instance. It will still fire up a brand new instance of Chromium. You would have to manually log in to all of those things. There are, there's this thing called browser dash use, which if you're trying to like scrape websites and pretend that you're a human, that seems to be what most people are using in this space. It's like kind of a step forward past puppeteer. And they also have hosted versions as well. If you need, just need a quick browser that's running in the cloud, you can pay them for that.

• 25:18Scott Tolinski?

  So limitations of this thing, like what can't you do? Wes mentioned already once that it doesn't have access to the accessibility issues. You know, there's tools out there that you can run on your code base that will check for accessibility markers and stuff like that. But having that in the browser would be super nice and super handy. Granted, you might be able to do some of that even, I know you can't do all these things, but at least like color checking and stuff, you might be able to do with the screenshots. But it does feel like it would be nice to just have that right baked in there.

• 25:47Wes Bos?

  Totally. And you can run like Lighthouse from the CLI to do those types of things. But since it is part of the DevTools, I would like access to that via the MCP server as well. And I also, like, I asked it, hey, check for accessibility issues. And all it did was just, it ran like 40 lines of JavaScript programmatically on the website and just checked for like aria labels and like text on all of them. It didn't do a great job that like something like the X suite or something would do. So I would like a little bit better accessibility tools built into this. And I kind of bet that that's that's coming at some point. And then there's direct access with all the CSS tooling as well.

• 26:31Wes Bos?

  I asked it, like, you know, when you open up your DevTools and you inspect element on like a H1 tag, it'd be nice to know, like, what color is it? And you can get all of these things with like Get Computed Style. And that's what it actually is doing when you ask it questions. But full access to the full CSS suite, you can see what CSS variables are. You can use, see which line of code things were written on. I think that would be really nice to have full access. And also like color.

• 27:04Scott Tolinski?

  So nice.

• 27:04Wes Bos?

  Yeah. Color issues, you know?

• 27:06Scott Tolinski?

  Yeah.

• 27:06Wes Bos?

  What's a good color for this? Change this color in dark mode, loop through all of my paragraph tags and make sure there's no, nothing there. It kind of gets more into the accessibility side of things, but.

• 27:16Scott Tolinski?

  And for this to work, AI would have to actually understand CSS, which we all know does not. It has no clue.

• 27:23Wes Bos?

  All it could do is a purple gradient in CSS. So that's all we got, an absolute position everything.

• 27:28Scott Tolinski?

  Yeah.

• 27:29Wes Bos?

  So that is the Chrome MCP server. Big fan of that. This is really exciting. I think these are probably early days for this type of thing. And I bet that more of these tools will start to show up over time. But certainly, check it out, throw it in your editor, throw it in your chat app. Even if you just like turn it off. I don't like having all my MCP servers turned on all the time. Because I feel like it just clutters the context. So I'll just turn them on project by project. As I need them, rather than having them turn on for absolutely everything, with the exception of like, maybe Contact 7.

• 28:02Scott Tolinski?

  Yeah, yeah, Contact 7, for sure. And I did want to say before we get out of here, Wes, while we were, I was checking out the new Spotlight tools that Sentry released, and this is not an ad read, but we were talking a little bit about the, like, the front-end logging and connecting all these things together. And the Spotlight by Sentry has an MCP now that I think would be very good for this, because you're still getting, like, Sentry's logging, you're getting it locally, and now you're getting an MCP to be able to connect to that. So, I, this is like, hot off the press, so I haven't gotten to use it yet. By the time you're hearing this, I'll have this deeply embedded into my project.

• 28:44Scott Tolinski?

  But I'm, I'm stoked on this, because like I said, the Sentry debugging tools have been very good with the AI, because they have so much data, and they understand how to use that data, so.

• 28:56Wes Bos?

  Contact, baby.

• 28:57Scott Tolinski?

  Give this a try, for sure, yeah.

• 28:59Wes Bos?

  All right, thanks everybody for tuning in, and we will catch you in the next one. Peace.

• 29:03Scott Tolinski?

  Peace.