Free tools Windows power users keep installed
One-click scans. No signup required.
Use Chrome DevTools MCP with Edge by pointing the server at the Edge executable, or auto-connect it to an Edge instance that was started with remote debugging. The same approach works with WebView2: identify the host application’s WebView2 user-data directory and let the server discover its DevTools endpoint. Launch mode is safer for an isolated test profile; auto-connect preserves a signed-in session but gives the agent access to that session’s cookies and page data.
What an Edge browser MCP server does
Microsoft’s guidance describes chrome-devtools-mcp as an MCP server for coding agents. Although the package is built for Chrome, it can control and inspect Chromium-based Microsoft Edge and WebView2 when configured with the correct executable or debugging endpoint. Through the browser’s DevTools Protocol, an agent can inspect pages, read console and network information, debug failures and profile performance while a page is open.
Edge’s DevTools Protocol is compatible with the Chrome DevTools Protocol. The MCP server uses Puppeteer to launch the configured browser, or reads the DevToolsActivePort file in a user-data directory to discover the WebSocket endpoint of an already-running browser.
Prerequisites
- Node.js, preferably the current Long-Term Support (LTS) release, with npm available on your PATH.
- Microsoft Edge Stable, Beta, Dev or Canary, or a WebView2 host application.
- An MCP-capable client such as Visual Studio Code with GitHub Copilot, Copilot CLI, Claude Code or Cursor.
- A separate browser profile if you will test authenticated or production-like flows. Do not expose your everyday profile to an agent unless you accept the data-access consequences.
Check the installations before configuring the client:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
node --version
npm --versionChoose a connection mode
| Mode | What happens | Best use | Main trade-off |
|---|---|---|---|
| Launch Edge | The MCP server starts the configured Edge binary, normally with an isolated profile. | Repeatable development, CI-like checks and work that should not touch personal sessions. | You must sign in again or seed test data in that profile. |
| Auto-connect to Edge | You start Edge with remote debugging; the server reads the user-data directory’s DevToolsActivePort information. |
Testing a flow that depends on an existing signed-in session. | The agent can reach tabs, cookies and data available to that profile. |
| Auto-connect to WebView2 | The server discovers the endpoint in the host application’s WebView2 data directory. | Inspecting a desktop application that embeds WebView2. | You must identify the correct host data directory and enable debugging for that app. |
| Playwright channel or CDP | Playwright launches an Edge channel such as msedge, or connects to a CDP endpoint. |
Accessibility-oriented automation and Playwright test suites. | This is a Playwright route rather than the Chrome DevTools MCP tool surface. |
Option 1: launch Edge from Chrome DevTools MCP
Launch mode is the clearest starting point because the server owns the browser process. Find the Edge executable for the installation you intend to test, then pass it to --executablePath. The exact location varies by Windows installation and channel, so use the path reported by your system rather than copying a path from another machine.
Run the server directly to verify that Node can start it:
npx chrome-devtools-mcp@latest --executablePath="C:pathtomsedge.exe"On macOS, the value is commonly the executable inside the Edge application bundle; on Linux it is the installed microsoft-edge binary. Quote paths containing spaces.
VS Code with GitHub Copilot
Add an MCP entry to the workspace or user mcp.json used by your VS Code installation:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →{
"servers": {
"edge-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest",
"--executablePath=C:\path\to\msedge.exe"
]
}
}
}Reload the window or restart the MCP session, then ask the agent to open a page and inspect it. Keep the executable path as one argument; on Windows, JSON requires doubled backslashes.
Copilot CLI, Claude Code, Cursor and other clients
These clients use slightly different configuration filenames, but the command is the same. In a generic mcpServers configuration, the equivalent entry is:
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
{
"mcpServers": {
"edge-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest",
"--executablePath=/absolute/path/to/edge"
]
}
}
}Copilot CLI uses an mcp-config.json-style file; Claude Code and Cursor expose their own MCP settings screens or configuration files. Preserve the same command and argument, but follow the client’s documented location and restart procedure.
Confirming a launch-mode connection
- Start or reload the MCP client after saving the configuration.
- Ask the agent to navigate to a harmless test page.
- Request a DOM inspection and a console-log check.
- If the browser does not appear, run the
npxcommand in a terminal and fix the first Node, permission or path error shown there.
Option 2: auto-connect to an existing Edge profile
Auto-connect is useful when the page requires an account, local storage or other state already present in Edge. Start a dedicated Edge instance with remote debugging enabled, then give the MCP server the matching user-data directory and --autoConnect.
Use a new data directory for agent work. A separate directory prevents accidental access to your normal browsing profile and makes the test reproducible. The exact remote-debugging startup syntax depends on your operating system and Edge channel; the important requirements are that Edge starts with remote debugging enabled and that the directory supplied to the server is the same one Edge uses.
npx chrome-devtools-mcp@latest
--autoConnect
--user-data-dir="/absolute/path/to/edge-agent-profile"On Windows PowerShell, keep the arguments on one line if your shell does not interpret the backslash continuation:
npx chrome-devtools-mcp@latest --autoConnect --user-data-dir="C:pathtoedge-agent-profile"When auto-connect is appropriate
- Use it for a test account whose cookies and local storage are intentionally available to the agent.
- Do not use it against a personal profile containing email, payment, corporate or production credentials.
- Stop the debugging-enabled Edge instance when the session is complete.
The agent can access information exposed through JavaScript APIs in the active session. This is the central security difference from launching a clean profile.
Option 3: connect to a WebView2 host
WebView2 applications embed the Edge rendering engine. Enable remote debugging for the host application, locate its WebView2 user-data directory (the directory name ends in EBWebView), and use the same auto-connect pattern:
Rank #3
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
npx chrome-devtools-mcp@latest
--autoConnect
--user-data-dir="/path/to/YourApp/EBWebView"If several WebView2 applications are running, close unrelated hosts and identify the directory belonging to the application under test. A wrong directory can leave the server with no endpoint or attach to a different app.
Playwright alternatives for Edge
If your workflow is primarily browser automation and accessibility assertions, Playwright can launch Edge by channel name: msedge, msedge-beta, msedge-dev or msedge-canary. It can also connect to a Chrome DevTools Protocol endpoint. This gives you Playwright’s locator and test APIs rather than the DevTools inspection-oriented tools exposed by Chrome DevTools MCP. Choose based on the task: DevTools MCP for agent-led inspection and debugging; Playwright for structured end-to-end tests.
Security and reliability checklist
- Least privilege: use a dedicated OS account or browser profile and a non-production login.
- Session isolation: launch mode is preferable when cookies and local storage are not required.
- Endpoint lifetime: auto-connect works only while the debugging-enabled browser and its user-data directory are available.
- State reset: delete and recreate a disposable profile when a test becomes contaminated by stale cookies or service-worker data.
- Version alignment: keep Node, Edge and the MCP package reasonably current; update deliberately when a stable setup matters.
- Resource use: full-page inspection, many open tabs and performance traces consume more memory than a single viewport check. Close tabs the agent does not need.
Troubleshooting common failures
npx or Node is not recognized
Install the current Node.js LTS release, reopen the terminal so PATH changes apply, and rerun node --version and npm --version.
Edge executable not found
The path is wrong, points to a shortcut rather than the binary, or targets a channel that is not installed. Locate the actual Edge executable and quote it, especially on Windows paths containing spaces.
The MCP client shows no tools
Validate JSON commas and escaping, confirm the client is reading the file you edited, and restart the MCP session. Run the same npx chrome-devtools-mcp@latest command manually to expose startup errors.
Auto-connect cannot find a browser
Confirm Edge was started with remote debugging, the process is still running, and --user-data-dir exactly matches the directory used at startup. For WebView2, use the host’s EBWebView directory, not a normal Edge profile.
Rank #4
- 5 in 1 Connectivity: The USB C Multiport Adapter is equipped with a 4K HDMI port, a 100W USB C PD port, a 5 Gbps USB A data port, and two 480 Mbps USB A ports
The agent sees the wrong account or page
Close other debugging-enabled instances, create a fresh profile, and sign in only with the intended test account. Auto-connect attaches to the available debugging session; it does not create a privacy boundary.
WebView2 attaches inconsistently
Exit the host application completely, relaunch it with debugging enabled, verify the EBWebView directory, and connect again. Multiple host processes can create ambiguity.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePages load but inspection is incomplete
Wait for the application’s own loading state, then ask the agent to inspect after navigation settles. Client-side rendering, cross-origin frames and permissions can limit what is visible from a particular context.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For a clean image or PDF of a URL rather than an interactive debugging session, ScreenshotNeo makes one request to its screenshot API. Its cleanup steps accept cookie-consent banners and remove more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing result.
See the complete parameter list in the ScreenshotNeo API documentation. A cURL capture looks like this:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info and capture_pdf tools, so Claude, Cursor and other MCP clients can request captures without browser-driver setup. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
FAQ
Is this a separate Edge-only MCP package?
No. The documented route uses chrome-devtools-mcp and points its Chromium browser configuration at Edge or a WebView2 endpoint.
Best Value
- Ultra-Fast Data Transfers: Experience the power of 5Gbps transfer speeds with this USB hub and sync data in seconds, making file transfers a breeze.
- Long Cable, Endless Convenience: Say goodbye to short and restrictive cables. This USB hub comes with a 2 ft long cable, giving you the freedom to connect your devices exactly where you need them.
- Sleek and Compact: Measuring just 4.2 × 1.2 × 0.4 inches, carry the USB hub in your pocket or laptop bag and connect effortlessly wherever you go.
- Instant Connectivity: Anker USB-C data hub offers a true plug-and-play experience, instantly connecting your devices and enabling seamless file transfers.
- What You Get: 2ft Anker USB-C Data Hub (4-in-1, 5Gbps) , welcome guide, our worry-free 18-month warranty, and friendly customer service.
Can I keep my existing Edge login?
Yes, with auto-connect and a debugging-enabled profile. Use a dedicated test profile because the connected agent can access that session’s browser data.
Does WebView2 require a different MCP protocol?
No. It uses the same DevTools connection pattern; the practical difference is finding the host application’s EBWebView user-data directory.
Should I use MCP or Playwright?
Use DevTools MCP when an agent must inspect and debug a live Chromium page. Use Playwright when you need repeatable locator-based automation and test assertions.
Frequently Asked Questions
Can an AI coding agent inspect a live Edge tab?
Yes, when Edge is started with remote debugging and Chrome DevTools MCP is configured with auto-connect to that profile.
What is the safest default configuration?
Launch Edge from the MCP server with a disposable user-data directory; it avoids exposing your everyday cookies and accounts.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
