Chrome DevTools MCP (2025) (developer.chrome.com)

Article summary

The Chrome DevTools MCP server has been enhanced to allow coding agents to directly connect to active browser sessions, enabling features like reusing existing browser sessions and accessing active debugging sessions. This feature is available in Chrome M144 and can be configured using the --autoConnect command line argument. The enhancement aims to improve productivity by allowing seamless transitions between manual and AI-assisted debugging. The feature requires remote debugging to be enabled in Chrome and user permission for each debugging session.

Main themes

• Chrome DevTools MCP
• Browser Automation
• AI-assisted Debugging
• Remote Debugging
• Coding Agents
• Browser Security

What commenters say

• The new feature is useful for automating tasks, but it also raises security concerns about potential misuse by malicious actors.
• Some users are already using similar tools and skills, such as Playwright CLI, and are satisfied with their functionality.
• The use of AI-generated content and comments is becoming increasingly prevalent and is seen as a problem by some users.
• Running Chromium in a Docker container can provide a secure and isolated environment for testing and debugging.
• The new feature may render CAPTCHAs less effective as a security measure.
• Some users are hesitant to switch to new tools and features due to the complexity and cost of token-based systems.
• The development of competing tools and features is driving innovation, but also creating confusion and difficulty in choosing the best option.
• Users are finding creative ways to work around limitations and improve the functionality of existing tools, such as using wrappers and custom skills.