<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Chrome on Mengboy Tech Notes</title>
    <link>https://www.mfun.ink/en/tags/chrome/</link>
    <description>Recent content in Chrome on Mengboy Tech Notes</description>
    <generator>Hugo -- 0.156.0</generator>
    <language>en</language>
    <lastBuildDate>Sun, 28 Dec 2025 22:26:08 +0800</lastBuildDate>
    <atom:link href="https://www.mfun.ink/en/tags/chrome/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Configure Chrome DevTools MCP in WSL</title>
      <link>https://www.mfun.ink/en/2025/12/28/chrome-devtools-mcp-wsl/</link>
      <pubDate>Sun, 28 Dec 2025 22:26:08 +0800</pubDate>
      <guid>https://www.mfun.ink/en/2025/12/28/chrome-devtools-mcp-wsl/</guid>
      <description>&lt;p&gt;Chrome DevTools MCP lets MCP clients connect to Chrome&amp;rsquo;s remote debugging endpoint. Because WSL2 and Windows are isolated at the network layer, you need port forwarding and a firewall rule. The commands below are split into clear steps.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
