DeepYard

Chrome DevTools MCP vs n8n MCP Server

Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.

Direct Answer

Chrome DevTools MCP suits teams needing open-source access, browser automation focus, and 49,556 GitHub stars in current listing data. n8n MCP Server suits teams needing open-source access, workflow creation focus, and 22,752 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.

What this comparison weighs

  • Pricing and free-tier availability
  • License model and deployment fit
  • GitHub adoption and contributor depth
  • Catalog tags, integrations, and supported workflows
C

Chrome DevTools MCP

Official Google MCP server giving coding agents full Chrome DevTools access — 28K+ stars

OSSFree
49.6Ktoday118
n

n8n MCP Server

Build n8n workflows from Claude Desktop, Cursor, or Claude Code — 14K+ stars

OSSFree
22.8K3d ago30
MetricChrome DevTools MCPn8n MCP Server
GitHub Stars49.6K22.8K
Contributors11830
Last CommitAug 21, 2026Aug 19, 2026
Open Issues9059
Licenseopen-sourceopen-source
Pricingopen-sourceopen-source
Free TierYesYes
Categorymcp-serversmcp-servers
TrendingNoNo

Choose Chrome DevTools MCP if you need

  • Chrome DevTools MCP is the stronger pick when Browser Automation matters because that capability is listed only on its profile.
  • Chrome DevTools MCP shows broader GitHub adoption with 49,556 stars versus 22,752 for n8n MCP Server.
  • Chrome DevTools MCP has a larger visible contributor base (118 vs 30).

Choose n8n MCP Server if you need

  • n8n MCP Server is the stronger pick when Workflow Creation matters because that capability is listed only on its profile.
  • n8n MCP Server is the cleaner fit if you specifically need N8n workflows from the catalog tags.

Meaningful differences

  • GitHub adoption: Chrome DevTools MCP shows 49,556 stars versus 22,752 for n8n MCP Server.
  • Contributor count: Chrome DevTools MCP lists 118 contributors and n8n MCP Server lists 30.

Shared capabilities

  • Automation

Shared Tags

automation

Only in Chrome DevTools MCP

chromedevtoolsdebuggingbrowsergoogleperformance

Only in n8n MCP Server

n8nworkflowno-code

Limitations and evidence

  • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
  • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
  • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.

About Chrome DevTools MCP

An official Google MCP server that gives AI coding agents full access to Chrome DevTools. Enables performance trace recording with actionable insights, advanced debugging (network requests, screenshots, console messages with source-mapped stack traces), and reliable Puppeteer-based browser automation with automatic result waiting. Supports headless mode for servers, isolated mode with temp user data, and WebSocket connection to existing Chrome instances.

View full listing

About n8n MCP Server

An MCP server that lets AI coding agents create, edit, and manage n8n workflows. Connect Claude Desktop, Cursor, or Claude Code to your n8n instance and build automations through natural language. Agents can create workflows, add nodes, configure connections, and activate automations without touching the n8n UI.

View full listing