chrome-devtools-mcp vs UI-TARS-desktop
chrome-devtools-mcp is the more adopted project, with 54,058 GitHub stars against 39,376 for UI-TARS-desktop. chrome-devtools-mcp was updated more recently (yesterday, against 15 days ago). Both are written in TypeScript.
| chrome-devtools-mcp | UI-TARS-desktop | |
|---|---|---|
| Description | Chrome DevTools for coding agents | The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra |
| Author | ChromeDevTools | bytedance |
| Stars | 54058 | 39376 |
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | Apache-2.0 |
| Last update | 2026-10-23T14:15:34Z | 2026-10-09T01:29:53Z |
| Source | https://github.com/ChromeDevTools/chrome-devtools-mcp | https://github.com/bytedance/UI-TARS-desktop |
| Stars this week | +343 | +73 |
Which should you choose?
- chrome-devtools-mcp describes itself as: "Chrome DevTools for coding agents"
- UI-TARS-desktop describes itself as: "The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra"
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 UI-TARS-desktop?
chrome-devtools-mcp has more GitHub stars: 54,058 against 39,376. This week chrome-devtools-mcp gained 343 stars and UI-TARS-desktop gained 73, which says more about current momentum than the all-time total. Both figures are refreshed daily from GitHub.
Are chrome-devtools-mcp and UI-TARS-desktop open source?
chrome-devtools-mcp: Apache-2.0 (open source). UI-TARS-desktop: Apache-2.0 (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 UI-TARS-desktop 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 UI-TARS-desktop
- chrome-devtools-mcp vs payload
- 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 · UI-TARS-desktop details · All Browser Automation MCP servers
Data last updated . Stars and downloads are refreshed every day from GitHub and npm.