Google’s Chrome DevTools MCP lets AI debug browsers; explore n8n‑MCP for AI workflow automation

Google has open‑sourced Chrome DevTools MCP, a tool that enables AI agents to control the Chrome browser, allowing generated code to be executed and debugged directly in Chrome.

With over 12 K stars on GitHub, the MCP server solves the problem of not seeing the runtime effect of AI‑generated code. It integrates Chrome’s debugging features for precise issue identification.

Compared with the previously recommended Playwright MCP, Chrome DevTools MCP is better suited for deep performance analysis, memory‑leak detection, and complex JavaScript debugging, while Playwright MCP focuses on cross‑browser automation and stable repeatable scripts.

Choosing the right tool

If you need detailed performance profiling, network request sequencing, memory‑leak tracing, or advanced JavaScript debugging, choose Chrome DevTools MCP.

If you need end‑to‑end automated testing across Chrome, Firefox, Safari, or stable user‑interaction scripting, consider Playwright MCP.

GitHub repository:

https://github.com/ChromeDevTools/chrome-devtools-mcp

n8n‑MCP: AI‑driven workflow builder

n8n‑MCP is an open‑source project designed for AI assistants like Claude Code to generate n8n workflows automatically. It provides over 500 nodes, 2 600+ template examples, and validation mechanisms tailored for AI‑generated workflows.

Key features include intelligent node search, real‑world configuration examples, comprehensive validation, template filtering, and fast query response (~12 ms).

It bridges AI models and the n8n automation platform, allowing AI assistants to understand and manipulate n8n nodes.

Typical use cases: quickly creating runnable workflows for users familiar with n8n; however, beginners without n8n experience may find it less useful.

GitHub repository:

https://github.com/czlonkowski/n8n-mcp