Comparison
chrome-devtools-mcp vs code-server
Verdict
Pick chrome-devtools-mcp if chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript; pick code-server if code-server offers VS Code functionality over the web enabling remote development with TypeScript. It is licensed under MIT.
Markdown twin · chrome-devtools-mcp alternatives · code-server alternatives
GraphCanon updated 2w
vs
Trust & integrity
| Signal | chrome-devtools-mcp | code-server |
|---|---|---|
| Maintenance | Very active (1d since push) As of 4w · github_public_v1 | Very active (3d since push) As of 2w · github_public_v1 |
| Provenance | Not a fork · Organization account As of 4w · github_public_v1 | Not a fork · Organization account As of 2w · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No published findings from this source as of 2026-07-11 As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- chrome-devtools-mcp
- Developer tools to enhance coding efficiency and debugging capabilities
- code-server
- VS Code in the browser
Stars
- chrome-devtools-mcp
- 48k
- code-server
- 79k
Forks
- chrome-devtools-mcp
- 3.2k
- code-server
- 6.8k
Open issues
- chrome-devtools-mcp
- 111
- code-server
- 161
Language
- chrome-devtools-mcp
- TypeScript
- code-server
- TypeScript
Adopt for
- chrome-devtools-mcp
- chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
- code-server
- code-server offers VS Code functionality over the web enabling remote development with TypeScript. It is licensed under MIT.
Persona
- chrome-devtools-mcp
- -
- code-server
- -
Runtime
- chrome-devtools-mcp
- -
- code-server
- -
License
- chrome-devtools-mcp
- Apache-2.0
- code-server
- MIT
Last pushed
- chrome-devtools-mcp
- Jul 24, 2026
- code-server
- Jul 30, 2026
Categories
- chrome-devtools-mcp
- Developer Tools
- code-server
- Developer Tools
Trust and health
Days since push
- chrome-devtools-mcp
- 1d
- code-server
- 3d
Open issues (now)
- chrome-devtools-mcp
- 111
- code-server
- 161
OSV dependency advisories
- chrome-devtools-mcp
- No lockfile (source not queried)
- code-server
- No published findings from this source as of 2026-07-11
Full report
- chrome-devtools-mcp
- Trust report
- code-server
- Trust report
Choose chrome-devtools-mcp if…
- License: chrome-devtools-mcp is Apache-2.0, code-server is MIT.
- Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging.
- chrome-devtools-mcp ships an MCP server manifest.
- - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome
When NOT to use chrome-devtools-mcp
- - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern
- - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
Choose code-server if…
- License: code-server is MIT, chrome-devtools-mcp is Apache-2.0.
- Tags unique to code-server: browser-ide, dev-tools, development-environment, ide.
- Need for browser-based access to VS Code
When NOT to use code-server
- Require full offline functionality since it is web-based and needs an internet connection
- System environments that prohibit the use of WebSockets due to security or compliance policies
- Looking for a more lightweight solution as setting up and running code-server comes with additional requirements beyond simple IDEs
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (ChromeDevTools/chrome-devtools-mcp) · observed Jul 26, 2026
- GitHub forks (ChromeDevTools/chrome-devtools-mcp) · observed Jul 26, 2026
- Last push (ChromeDevTools/chrome-devtools-mcp) · observed Jul 24, 2026
- License file (Apache-2.0) · observed Jul 26, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (coder/code-server) · observed Aug 3, 2026
- GitHub forks (coder/code-server) · observed Aug 3, 2026
- Last push (coder/code-server) · observed Jul 30, 2026
- License file (MIT) · observed Aug 3, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: chrome-devtools-mcp 48k · code-server 79k (synced Jul 26, 2026).
Common questions
- What is the difference between chrome-devtools-mcp and code-server?
- chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. code-server: VS Code in the browser. See the comparison table for live GitHub stats and shared categories.
- When should I choose chrome-devtools-mcp over code-server?
- Choose chrome-devtools-mcp over code-server when License: chrome-devtools-mcp is Apache-2.0, code-server is MIT; Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging; chrome-devtools-mcp ships an MCP server manifest; - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome.
- When should I choose code-server over chrome-devtools-mcp?
- Choose code-server over chrome-devtools-mcp when License: code-server is MIT, chrome-devtools-mcp is Apache-2.0; Tags unique to code-server: browser-ide, dev-tools, development-environment, ide; Need for browser-based access to VS Code.
- When should I avoid chrome-devtools-mcp?
- - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
- When should I avoid code-server?
- Require full offline functionality since it is web-based and needs an internet connection System environments that prohibit the use of WebSockets due to security or compliance policies Looking for a more lightweight solution as setting up and running code-server comes with additional requirements beyond simple IDEs
- Is chrome-devtools-mcp or code-server more popular on GitHub?
- code-server has more GitHub stars (78,598 vs 47,594). Stars measure visibility, not whether either tool fits your constraints.
- Are chrome-devtools-mcp and code-server open source?
- Yes - both are open-source projects on GitHub (chrome-devtools-mcp: Apache-2.0, code-server: MIT).
- Where can I find alternatives to chrome-devtools-mcp or code-server?
- GraphCanon lists graph-backed alternatives at chrome-devtools-mcp alternatives and code-server alternatives (chrome-devtools-mcp markdown twin, code-server markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, chrome-devtools-mcp or code-server?
- chrome-devtools-mcp: Very active. code-server: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for chrome-devtools-mcp and code-server?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chrome-devtools-mcp trust report; code-server trust report.