head to head · open source

chrome-devtools-mcp vs VideoTogether

chrome-devtools-mcp has 54,665 GitHub stars, 5,250 forks, 109 open issues and last shipped yesterday. VideoTogether has 1,794 stars, 123 forks, 18 open issues and last shipped 9 months ago. chrome-devtools-mcp leads on adoption by 2,947% (54,665 vs 1,794 stars). chrome-devtools-mcp is written in TypeScript under Apache-2.0; VideoTogether is written in JavaScript under MIT. chrome-devtools-mcp has attracted 10% as many forks as stars, VideoTogether 7%. chrome-devtools-mcp was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

chrome-devtools-mcp ★ 55K VideoTogether ★ 1.8K category Productivity & Utilities

← all 20902 open source comparisons

Side by side

chrome-devtools-mcp VideoTogether
GitHub stars ★ 55K ★ 1.8K
License Apache-2.0 MIT
Written in TypeScript JavaScript
Last push 2026-11-02 2026-02-09
Forks ⑂ 5.3K ⑂ 123
Self-hosting Yes Yes
Data ownership Your server Your server

pick chrome-devtools-mcp if

  • You weight community size — 55K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full chrome-devtools-mcp profile →

pick VideoTogether if

  • You want the VideoTogether feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches JavaScript
  • You evaluated both and VideoTogether fits your workflow better

full VideoTogether profile →

About chrome-devtools-mcp

Chrome DevTools for agents Chrome DevTools for agents ( chrome devtools mcp ) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model Context Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in depth debugging, and performance analysis. A [CLI][cli] is also provided for use without MCP. [Tool reference][tool reference] [Changelog][changelog] [Contributing][contributing] [Troubleshooting][troubleshooting] [Design Principles][design principles] Key features Get…

read the full chrome-devtools-mcp overview →

About VideoTogether

VideoTogether VideoTogether is a browser extension that syncs video playback with friends in real time on Chrome, Edge, and Safari. Visit for more information [ English ] [中文 ] Installation Please visit our website for installation guide Development Extension The core code is main/source/extension/vt.js We use a very simple compile script script/build extension.py to build run python script/build extension.py to build, the output directory is ./release Service service code is in source/go server

read the full VideoTogether overview →

More in Productivity & Utilities

Related comparisons

More Browsers & Extensions projects

Compare either of these against the rest of the Browsers & Extensions field.

Frequently asked questions

Is chrome-devtools-mcp or VideoTogether more popular?

chrome-devtools-mcp has 54,665 GitHub stars and VideoTogether has 1,794. chrome-devtools-mcp has the larger community by that measure.

Are chrome-devtools-mcp and VideoTogether free?

Both are open source. chrome-devtools-mcp is licensed under Apache-2.0 and VideoTogether under MIT. Neither carries a licence fee.

What is the difference between chrome-devtools-mcp and VideoTogether?

chrome-devtools-mcp is written in TypeScript and VideoTogether in JavaScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, chrome-devtools-mcp or VideoTogether?

Choose chrome-devtools-mcp if you want the larger community (54,665 stars) or its Apache-2.0 licence terms. Choose VideoTogether if its feature set, stack or MIT licence fits better. Both are self-hostable.