chrome-devtools-mcp vs payload
chrome-devtools-mcp is the more adopted project, with 54,058 GitHub stars against 45,459 for payload. payload was updated more recently (today, against yesterday). Both are written in TypeScript.
| chrome-devtools-mcp | payload | |
|---|---|---|
| Description | Chrome DevTools for coding agents | Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building |
| Author | ChromeDevTools | payloadcms |
| Stars | 54058 | 45459 |
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | MIT |
| Last update | 2026-10-23T14:15:34Z | 2026-10-24T03:29:07Z |
| Source | https://github.com/ChromeDevTools/chrome-devtools-mcp | https://github.com/payloadcms/payload |
| Stars this week | +343 | n/a |
Which should you choose?
- chrome-devtools-mcp describes itself as: "Chrome DevTools for coding agents"
- payload describes itself as: "Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin..."
Stars measure adoption, not fit. Read both READMEs for the tools each server exposes, then try them side by side in your client: the install guide shows how to add both.
Frequently asked questions
Which is more popular, chrome-devtools-mcp or payload?
chrome-devtools-mcp has more GitHub stars: 54,058 against 45,459. This week chrome-devtools-mcp gained 343 stars and payload gained 0, which says more about current momentum than the all-time total. Both figures are refreshed daily from GitHub.
Are chrome-devtools-mcp and payload open source?
chrome-devtools-mcp: Apache-2.0 (open source). payload: MIT (open source). An open-source license lets you run and self-host the server at no cost. If either one wraps a commercial API, that provider's pricing still applies, so read each README for the accounts and keys it needs.
Can I use chrome-devtools-mcp and payload together?
Yes, if both run as MCP servers. MCP clients such as Claude Code, Cursor and VS Code can connect to several servers at once, and the agent picks tools from each. Give them distinct names in your config, and keep the number of active servers small so tool definitions do not crowd the context window.
Related comparisons
- browser-use vs chrome-devtools-mcp
- browser-use vs payload
- chrome-devtools-mcp vs UI-TARS-desktop
- chrome-devtools-mcp vs invisible_dots
- chrome-devtools-mcp vs quasar
- chrome-devtools-mcp vs browser-harness
- chrome-devtools-mcp vs codex-chatgpt-web
- payload vs UI-TARS-desktop
chrome-devtools-mcp details · payload details · All Browser Automation MCP servers
Data last updated . Stars and downloads are refreshed every day from GitHub and npm.